CVE-2025-30208
Vite, a provider of frontend development tooling, has a vulnerability in versions prior to 6.2.3, 6.1.2, 6.0.12, 5.4.15, and 4.5.10. `@fs` denies access to files outside of Vite serving allow list. Adding `?raw??` or `?import&raw??` to the URL bypasses this limitation and returns the file content if it exists. This bypass exists because trailing separators such as `?` are removed in several places, but are not accounted for in query string regexes. The contents of arbitrary files can be returned to the browser. Only apps explicitly exposing the Vite dev server to the network (using `--host` or `server.host` config option) are affected. Versions 6.2.3, 6.1.2, 6.0.12, 5.4.15, and 4.5.10 fix the issue.
- CVSS
- 5.3Mediumscored by the publisher (CNA)
- Exploited in the wild
- Not knownPublic exploit code; not in CISA KEV
- EPSS
- 74.8%chance of exploitation in the next 30 daystop 0.5% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 24 Mar 2025analysed here 12 Nov 2026
Summary
Triage
- Attack surface
- Server-side
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- Partly. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| vitejs vite | < 4.5.10>= 5.0.0 and < 5.4.15>= 6.0.0 and < 6.0.12>= 6.1.0 and < 6.1.2>= 6.2.0 and < 6.2.3Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- vitejs:vite
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 1 rule (Block) · since 29 Sept 2025
- Vite - Directory Traversal - CVE:CVE-2025-30208 · Cloudflare Managed Ruleset
Also consider: patch · enable the vendor rule in block mode · response filtering
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Yes: 1 on Exploit-DB · 24 GitHub proofs of concept · 1 Nuclei template
- CISA SSVC
- exploitation poc, automatable no, technical impact partialAssessed by CISA 24 Mar 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Exploit-DB
- Vite 6.2.2 - Arbitrary File Readremote, 3 Apr 2025
Nuclei
- Vite - Arbitrary File Readdetection template, medium
GitHub proofs of concept
- ThumpBo/CVE-2025-30208-EXP194 stars
- xuemian168/CVE-2025-3020850 stars
- 4xura/CVE-2025-3020812 stars
- marino-admin/Vite-CVE-2025-30208-Scanner10 stars
and 20 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 24 Mar 2025Published
- 24 Mar 2025CISA SSVC assessment: exploitation pocsame day later
- 24 Mar 2025CVE record last updatedsame day later
- 26 Mar 2025First public exploit or proof of concept1 day later
- 12 Nov 2026Analysed by vulneraibility.com597 days (about 2 years) later
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | HighNeeds specific conditions, a race or a particular configuration. | Needs specific conditions, a race or a particular configuration. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | RequiredA victim must click, open or otherwise cooperate. | A victim must click, open or otherwise cooperate. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | NoneNo unauthorised modification. | No unauthorised modification. |
| Availability | NoneThe service stays up. | The service stays up. |
Common questions
Is CVE-2025-30208 being exploited?
Not confirmed. CVE-2025-30208 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 75% probability of exploitation in the next 30 days.
How severe is CVE-2025-30208?
CVE-2025-30208 is rated Medium with a CVSS score of 5.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-30208?
Yes. A fix has been recorded for CVE-2025-30208. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-30208 affect?
CVE-2025-30208 affects vitejs:vite. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
6 references in the CVE record, grouped by the tags the record gives them.
Other links (6)
- github.com /vitejs/vite/security/advisories/GHSA-x574-m823-4x7w
- github.com /vitejs/vite/commit/315695e9d97cc6cfa7e6d9e0229fb50cdae3d9f4
- github.com /vitejs/vite/commit/80381c38d6f068b12e6e928cd3c616bd1d64803c
- github.com /vitejs/vite/commit/807d7f06d33ab49c48a2a3501da3eea1906c0d41
- github.com /vitejs/vite/commit/92ca12dc79118bf66f2b32ff81ed09e0d0bd07ca
- github.com /vitejs/vite/commit/f234b5744d8b74c95535a7b82cc88ed2144263c1
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.