Skip to content
Fencer Intel
medium 5.3

CVE-2025-24361 json

Opening a malicious website while running a Nuxt dev server could allow read-only access to code

published last yr. modified 4mo ago also EUVD-2025-0132 , GHSA-4gf7-ff8x-hq99

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

Nuxt is an open-source web development framework for Vue.js. Source code may be stolen during dev when using version 3.0.0 through 3.15.12 of the webpack builder or version 3.12.2 through 3.152 of the rspack builder and a victim opens a malicious web site. Because the request for classic script by a script tag is not subject to same origin policy, an attacker can inject a malicious script in their site and run the script. By using `Function::toString` against the values in `window.webpackChunknuxt_app`, the attacker can get the source code. Version 3.15.13 of Nuxt patches this issue.

Patch / fix

  • npm @nuxt/webpack-builder 3.15.3
  • npm @nuxt/rspack-builder 3.15.3
  • nuxt nuxt 3.15.3
  • nuxt rspack_builder 3.15.3
  • nuxt webpack_builder 3.15.3

Is CVE-2025-24361 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm @nuxt/webpack-builder
>=3.0.0, <3.15.3
3.15.3
npm @nuxt/rspack-builder
>=3.12.2, <3.15.3
3.15.3

Affected products

  • nuxt nuxt

Classification

Weakness
  • CWE-749 Exposed Dangerous Method or Function

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.