Source-code disclosure via wildcard CORS policy
Published Jan 25, 2025 · Updated Feb 12, 2025
Information disclosure in Nuxt 3.8.1 through 3.15.2 allows remote attackers to read development-server source code via a malicious website. The Vite builder's default CORS handler sets Access-Control-Allow-Origin to a wildcard, so cross-origin browser fetches can read responses such as /_nuxt/app.vue. Exploitation requires a developer to run the Vite-based development server with default CORS settings and open an attacker-controlled page; the documented impact is read-only source disclosure.
Summary
What happened
Information disclosure in Nuxt 3.8.1 through 3.15.2 allows remote attackers to read development-server source code via a malicious website. The Vite builder's default CORS handler sets Access-Control-Allow-Origin to a wildcard, so cross-origin browser fetches can read responses such as /_nuxt/app.vue. Exploitation requires a developer to run the Vite-based development server with default CORS settings and open an attacker-controlled page; the documented impact is read-only source disclosure.
The record
- CVE
- CVE-2025-24360
- Published
- Jan 25, 2025
- Updated
- Feb 12, 2025
- Vendor
- Nuxt
- Product
- Nuxt
- Classifications
- CWE-200, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.8.1, < 3.15.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Cross-origin Nuxt development asset fetch proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo