Threats / Vite / CVE-2025-31125
CVE-2025-31125
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-07
Vite Vitejs vulnerability
Vite dev server contains an improper access control vulnerability allowing unauthorized file content exposure through query parameters when the server is exposed to the network.
Verdict
Today item — known-exploited.
An attacker on the network can bypass access controls in Vite's dev server to read non-allowed files by manipulating inline and raw import query parameters, affecting applications with network-exposed dev servers.
CISA KEV Yes · 2026-01-225EPSS 0.58801 (verify live)6Exploit Public PoC7CVSS 5.33CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-01-22).
Probability (EPSS)
EPSS 0.58801 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.3 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N) · Affected: Vite, Vitejs. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-200 Information Exposure, CWE-284 Improper Access Control — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 297 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
WeaknessCWE-200 · Information ExposureCWE-284 · Improper Access ControlAuthorization / access control
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft HTTP requests with ?inline&import or ?raw?import query parameters to the exposed Vite dev server.
Business
Source code, configuration files, and other sensitive application content become readable to network-based attackers.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I enumerate accessible files by testing various paths and parameter combinations against the dev server.
Business
Intellectual property and secrets embedded in the codebase are compromised, increasing breach scope and regulatory exposure.
3
Lateral reach — past segmentation narrative 3
Attacker
I extract environment variables, API keys, or database credentials visible in exposed configuration or source files.
Business
Downstream systems and services become compromised, enabling lateral movement and further infrastructure attacks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by GitHub_MCNA
Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.