https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 23 Oct 2026 16:42:07 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-158239 EUVD-2026-158239 https://cve.radiocsirt.org/vuln/euvd-2026-158239 https://cve.radiocsirt.org/vuln/fkie_cve-2024-34344 <p>Nuxt is a free and open-source framework to create full-stack web applications and websites with Vue.js. Due to the insufficient validation of the `path` parameter in the NuxtTestComponentWrapper, an attacker can execute arbitrary JavaScript on the server side, which allows them to execute arbitrary commands. Users who open a malicious web page in the browser while running the test locally are affected by this vulnerability, which results in the remote code execution from the malicious web page. Since web pages can send requests to arbitrary addresses, a malicious web page can repeatedly try to exploit this vulnerability, which then triggers the exploit when the test server starts.</p> <p>Nuxt is a free and open-source framework to create full-stack web applications and websites with Vue.js. Due to the insufficient validation of the `path` parameter in the NuxtTestComponentWrapper, an attacker can execute arbitrary JavaScript on the server side, which allows them to execute arbitrary commands. Users who open a malicious web page in the browser while running the test locally are affected by this vulnerability, which results in the remote code execution from the malicious web page. Since web pages can send requests to arbitrary addresses, a malicious web page can repeatedly try to exploit this vulnerability, which then triggers the exploit when the test server starts.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-34344 https://cve.radiocsirt.org/vuln/ghsa-v784-fjjh-f8r4 <p><strong>Affected:</strong> npm: nuxt</p> <p>### Summary Due to the insufficient validation of the `path` parameter in the NuxtTestComponentWrapper, an attacker can execute arbitrary JavaScript on the server side, which allows them to execute arbitrary commands.</p> <p>### Details While running the test, a special component named `NuxtTestComponentWrapper` is available. https://github.com/nuxt/nuxt/blob/4779f5906fa4d3c784c2e2d6fe5a5c5f181faaec/packages/nuxt/src/app/components/nuxt-root.vue#L42-L43</p> <p>This component loads the specified path as a component and renders it.</p> <p>https://github.com/nuxt/nuxt/blob/4779f5906fa4d3c784c2e2d6fe5a5c5f181faaec/packages/nuxt/src/app/components/test-component-wrapper.ts#L9-L27</p> <p>There is a validation for the `path` parameter to check whether the path traversal is performed, but this check is not sufficient.</p> <p>https://github.com/nuxt/nuxt/blob/4779f5906fa4d3c784c2e2d6fe5a5c5f181faaec/packages/nuxt/src/app/components/test-component-wrapper.ts#L15-L19</p> <p>Since `import(...)` uses `query.path` instead of the normalized `path`, a non-normalized URL can reach the `import(...)` function. For example, passing something like `./components/test` normalizes `path` to `/root/directory/components/test`, but `import(...)` still receives `./components/test`.</p> <p>By using this behavior, it&#39;s possible to load arbitrary JavaScript by using the path like the following: ``` data:text/javascript;base64,Y29uc29sZS5sb2coMSk ```</p> <p>Since `resolve(...)` resolves the filesystem path, not the URI, the above URI is treated as a rel…</p> <p><strong>Affected:</strong> npm: nuxt</p> <p>### Summary Due to the insufficient validation of the `path` parameter in the NuxtTestComponentWrapper, an attacker can execute arbitrary JavaScript on the server side, which allows them to execute arbitrary commands.</p> <p>### Details While running the test, a special component named `NuxtTestComponentWrapper` is available. https://github.com/nuxt/nuxt/blob/4779f5906fa4d3c784c2e2d6fe5a5c5f181faaec/packages/nuxt/src/app/components/nuxt-root.vue#L42-L43</p> <p>This component loads the specified path as a component and renders it.</p> <p>https://github.com/nuxt/nuxt/blob/4779f5906fa4d3c784c2e2d6fe5a5c5f181faaec/packages/nuxt/src/app/components/test-component-wrapper.ts#L9-L27</p> <p>There is a validation for the `path` parameter to check whether the path traversal is performed, but this check is not sufficient.</p> <p>https://github.com/nuxt/nuxt/blob/4779f5906fa4d3c784c2e2d6fe5a5c5f181faaec/packages/nuxt/src/app/components/test-component-wrapper.ts#L15-L19</p> <p>Since `import(...)` uses `query.path` instead of the normalized `path`, a non-normalized URL can reach the `import(...)` function. For example, passing something like `./components/test` normalizes `path` to `/root/directory/components/test`, but `import(...)` still receives `./components/test`.</p> <p>By using this behavior, it&#39;s possible to load arbitrary JavaScript by using the path like the following: ``` data:text/javascript;base64,Y29uc29sZS5sb2coMSk ```</p> <p>Since `resolve(...)` resolves the filesystem path, not the URI, the above URI is treated as a rel…</p> https://cve.radiocsirt.org/vuln/ghsa-v784-fjjh-f8r4