Vigilbase CVEConnect your agent

Vite bypasses server.fs.deny when using `?raw??`

Not in CISA KEVPublic exploit codeCVE-2025-30208CWE-200CWE-284

Not confirmed exploited. 3 of 8 rule sources name it; Cloudflare blocks by default. Our CRS test: not blocked.

Edge rules
3/8
Our test
Not blocked
CVSS
5.3
EPSS
74.8% Top 0.5%
Posts, 14d
02026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts
Published
2025-03-24
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… More

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.

Ask Vigil

AI · answers from this page
Ask about CVE-2025-30208: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1
Medium · 5.3 / 10

Exploitable over the network under specific conditions, with no privileges and user interaction, leading to full loss of confidentiality.

Over the internetNo login neededNeeds a user to actHard to pull offSerious impact
How the score is built8 metrics
  • Attack vectorAn attacker can reach it over the internet; no access to your network needed.
    Network
  • Attack complexityThe attack only works when conditions outside the attacker's control line up.
    High
  • Privileges requiredNo account or login is needed.
    None
  • User interactionA user has to do something first, such as open a file or click a link.
    Required
  • ScopeThe damage stays within the vulnerable component.
    Unchanged
  • Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
    High
  • Integrity impactData cannot be changed by the attacker.
    None
  • Availability impactThe component keeps working normally.
    None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
CISA's assessmentSSVC, from the CVE record
ExploitationProof of concept

Public exploit code or a detailed write-up exists, but CISA has not seen attacks.

AutomatableNo

At least one step needs hands-on work, which slows mass attacks.

Technical impactPartial

A successful attack gives limited control over the affected software or limited access to its data.

Public exploits

2 found
0 Metasploit1 Exploit-DB1 Scanner template0 GitHub PoCs

Links are to third-party code: never run it outside an isolated lab.

Timeline

  1. 2025-03-24
    CVE published
    CVE List
  2. 2025-04-03
    Exploit published on Exploit-DB
    Vite 6.2.2 - Arbitrary File Read
  3. 2025-04-28
    F5 ships a rule
    Vite Framework Arbitrary File Read (1)
  4. 2025-09-29
    Cloudflare ships a rule
    Vite - Directory Traversal - CVE:CVE-2025-30208
  5. 2026-03-04
    OWASP CRS ships a rule
    feat(lfi): Add detection for Vite.js path traversal (CVE-2025-30208) (https://github.com/coreruleset/coreruleset/pull/4407)
  6. 2026-11-02
    Our test: OWASP Core Rule Set let it through
    paranoia level 1, anomaly threshold 5, default CRS settings
  7. 2026-11-02
    Our test: OWASP Core Rule Set let it through
    paranoia level 2, anomaly threshold 5, default CRS settings

Social

2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts

No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.

Vendor statements

Quoted
CloudflareWAF Managed Rules1 quoteBlocks by default

First rule 2025-09-29, 189 days after the CVE was published.

2025-09-29New rule…ddc329ddDefault: BlockSource
Vite - Directory Traversal - CVE:CVE-2025-30208. Previous action: Log. New action: Block. This is a New Detection
AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)3 quotesRule published

First rule 2025-04-28, 35 days after the CVE was published.

2025-04-28New rule200009326Source
Added: signature 200009326 "Vite Framework Arbitrary File Read (1)" (Information Leakage, risk High), systems: JavaScript. References: CVE-2025-30208.
2025-04-28New rule200009327Source
Added: signature 200009327 "Vite Framework Arbitrary File Read (2)" (Information Leakage, risk High), systems: JavaScript. References: CVE-2025-30208.
2025-05-22New rule200009327Source
Added: signature 200009327 "Vite Framework Arbitrary File Read (2)" (Information Leakage, risk High), systems: JavaScript. References: CVE-2025-30208, CVE-2025-31125.
AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)1 quoteRule published

First rule 2026-03-04, 345 days after the CVE was published.

2026-03-04New ruleSource
feat(lfi): Add detection for Vite.js path traversal (CVE-2025-30208) (https://github.com/coreruleset/coreruleset/pull/4407)