CVE-2025-30208

MEDIUMNVD 5.39.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 90% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
5.3
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 75%
CISA-KEV: Not listedEPSS: 75%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
5.3
EG Score
9.0(high)
EG Risk
—
EPSS
99.5%
KEV
Not listed

Published

March 24, 2025

Last Modified

September 23, 2025

References (6)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
vite—4.5.10—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-20 17:07 UTCEPSS rescore
  4. 2026-07-16 17:02 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-13 06:12 UTCEPSS rescore
  8. 2026-07-13 06:12 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-08 15:14 UTCEPSS rescore
  14. 2026-07-07 06:51 UTCOSV refresh
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 16:26 UTCEPSS rescore
  17. 2026-07-04 06:30 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 23:21 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 04:55 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 23 more
  1. 2026-06-24 14:04 UTCEPSS rescore
  2. 2026-06-24 14:04 UTCEPSS rescore
  3. 2026-06-23 21:32 UTCEPSS rescore
  4. 2026-06-23 21:32 UTCEPSS rescore
  5. 2026-06-18 17:43 UTCOSV refresh
  6. 2026-06-17 17:52 UTCEPSS rescore
  7. 2026-06-15 17:48 UTCEPSS rescore
  8. 2026-06-13 23:00 UTCEPSS rescore
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-10 22:18 UTCEPSS rescore
  11. 2026-06-07 15:24 UTCEPSS rescore
  12. 2026-06-07 15:24 UTCEPSS rescore
  13. 2026-06-06 13:47 UTCEPSS rescore
  14. 2026-06-06 13:47 UTCEPSS rescore
  15. 2026-06-05 22:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-05 06:10 UTCEPSS rescore
  18. 2026-06-05 06:10 UTCEPSS rescore
  19. 2026-06-04 13:12 UTCEPSS rescore
  20. 2026-06-04 13:11 UTCEPSS rescore
  21. 2026-06-02 20:12 UTCEPSS rescore
  22. 2026-05-30 08:58 UTCEG score recompute
  23. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCThemeHackers/CVE-2025-30208
    First seen Jun 27, 2025

    CVE‑2025‑30208 is a medium-severity arbitrary file read vulnerability in the Vite development server (a popular frontend build tool)

    Open source ↗
  • GitHub PoCnkuty/CVE-2025-30208-31125-31486-32395
    First seen May 29, 2025
    Open source ↗
  • GitHub PoCr0ngy40/CVE-2025-30208-Series
    First seen Apr 24, 2025

    Analysis of the Reproduction of CVE-2025-30208 Series Vulnerabilities

    Open source ↗
  • Exploit-DBEDB-52111
    First seen Apr 3, 2025

    Vite 6.2.2 - Arbitrary File Read

    Open source ↗
  • GitHub PoC4m3rr0r/CVE-2025-30208-PoC
    First seen Apr 3, 2025

    CVE-2025-30208 - Vite Arbitrary File Read PoC

    Open source ↗
  • GitHub PoCjackieya/ViteVulScan
    First seen Mar 31, 2025

    针对CVE-2025-30208和CVE-2025-31125的漏洞利用

    Open source ↗
  • GitHub PoC4xura/CVE-2025-30208
    First seen Mar 27, 2025

    A PoC of the exploit script for the Arbitrary File Read vulnerability of Vite /@fs/ Path Traversal in the transformMiddleware (CVE-2025-30208).

    Open source ↗
  • GitHub PoCOn1onss/CVE-2025-30208
    First seen Mar 27, 2025

    This exploit is for educational and ethical security testing purposes only. The use of this exploit against targets without prior mutual consent is illegal, and the developer disclaims any liability for misuse or damage caused by this exploit.

    Open source ↗
  • GitHub PoCAakiTT/CVE-2025-30208
    First seen Mar 26, 2025

    CVE-2025-30208漏洞验证工具

    Open source ↗
  • GitHub PoCThumpBo/CVE-2025-30208-EXP
    First seen Mar 26, 2025

    CVE-2025-30208-EXP

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-30208?
CVE-2025-30208 is a medium vulnerability published on March 24, 2025. 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…
When was CVE-2025-30208 disclosed?
CVE-2025-30208 was first published in the National Vulnerability Database on March 24, 2025, with the most recent update on September 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-30208 actively exploited?
CVE-2025-30208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-30208?
CVE-2025-30208 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2025-30208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-30208, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-30208

Explore →

Is Your Infrastructure Affected by CVE-2025-30208?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs