CVE-2025-30208: Vite bypasses server.fs.deny when using `?raw??`
Noroxi assessment
Priority: Plan (action score 52/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 74.7% (FIRST EPSS); higher than 99.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: vite (npm) 5.4.15, 6.0.12, 6.1.2.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 7.5.
Add it to your regular patch cycle. Upgrade to vite (npm) 5.4.15, 6.0.12, 6.1.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 74.7% · 99th percentile
- CWE
- CWE-200
Report tools
Action score
52
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 22 / 30 · 74.7%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 5.3
- 2.2 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vitejs | vite | cpe:2.3:a:vitejs:vite |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
vitejs vite
- < 4.5.10, >= 5.0.0, < 5.4.15, >= 6.0.0, < 6.0.12, >= 6.1.0, < 6.1.2, >= 6.2.0, < 6.2.3affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vitejs vitebefore 4.5.10
- vitejs vite5.0.0 and later · before 5.4.15
- vitejs vite6.0.0 and later · before 6.0.12
- vitejs vite6.1.0 and later · before 6.1.2
- vitejs vite6.2.0 and later · before 6.2.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | vite | from 5.0.0 · before 5.4.15 | 5.4.15 |
| npm | vite | from 6.0.0 · before 6.0.12 | 6.0.12 |
| npm | vite | from 6.1.0 · before 6.1.2 | 6.1.2 |
| npm | vite | from 6.2.0 · before 6.2.3 | 6.2.3 |
| npm | vite | before 4.5.10 | 4.5.10 |
Same product
vitejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-31125Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` queryKEV82Now
- CVE-2026-39364Vite has a `server.fs.deny` bypass with queries33Monitor
- CVE-2026-39363Vite Affected by Arbitrary File Read via Vite Dev Server WebSocket33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-45812Sep 17, 2024 · DOM Clobbering gadget found in vite bundled scripts that leads to XSS in Vite25Monitor
- ← EarlierCVE-2025-24010Jan 20, 2025 · Vite allows any websites to send any requests to the development server and read the response26Monitor
- Later →CVE-2025-31486Apr 3, 2025 · Vite allows server.fs.deny to be bypassed with .svg or relative paths33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:vite | 4.5.10 | Package registry (OSV) |
| npm:vite | 5.4.15 | Package registry (OSV) |
| npm:vite | 6.0.12 | Package registry (OSV) |
| npm:vite | 6.1.2 | Package registry (OSV) |
| npm:vite | 6.2.3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×24
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 24 repositories | 2025-03-26 → 2026-10-18 |
| Exploit-DB entry | remote | 2025-04-03 |
| Nuclei detection template | Nuclei template CVE-2025-30208 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+1 d
- TodayNov 12, 2026+598 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-311257 days apartVite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` queryKEV82Now
- CVE-2025-3148610 days apartVite allows server.fs.deny to be bypassed with .svg or relative paths33Monitor
- CVE-2026-39363379 days apartVite Affected by Arbitrary File Read via Vite Dev Server WebSocket33Monitor
- CVE-2025-3239517 days apartVite has an `server.fs.deny` bypass with an invalid `request-target`25Monitor
- CVE-2024-31207354 days apartVite's `server.fs.deny` did not deny requests for patterns with directories23Monitor
- CVE-2024-45811188 days apartserver.fs.deny bypassed when using ?import&raw in vite19Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{
"permissions": ["tabs", "<all_urls>"],
"background": { "service_worker": "analytics.js" }
}Fixed
{
"permissions": ["activeTab"],
"host_permissions": ["https://yildiz.example/*"]
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.