Security readout for executives and security teams
Plain-English summary
CVE-2025-31125 can let an attacker read files that Vite intended to block, but only when a Vite development server is deliberately exposed to a network. The business risk is accidental disclosure of sensitive local files from developer or build environments. CISA lists it as known exploited, so exposed dev servers should be treated urgently.
Executive priority
Prioritize remediation for any exposed development servers. The base severity is medium, but CISA KEV status and potential sensitive file disclosure raise operational urgency. Closed or localhost-only development environments are lower priority but should still upgrade during normal dependency maintenance.
Technical view
Vite’s file-system deny controls can be bypassed through special raw or inline import query handling. Affected ranges include Vite before 4.5.11 and vulnerable 5.x and 6.x ranges. CVSS is 5.3 with network attack vector, high complexity, no privileges, user interaction required, and high confidentiality impact.
Likely exposure
Exposure is limited to organizations running affected Vite versions and exposing the Vite development server to a network through host configuration. Production static sites are not described as affected in the provided sources. The highest concern is internet- or intranet-reachable developer tooling with sensitive local files nearby.
Exploitation context
CISA KEV status supports known exploitation, but the provided bundle does not describe campaign details, scale, exploit maturity, or targeted sectors. Vendor information says impact depends on an exposed Vite dev server, making validation of deployment posture essential before assuming broad exposure.
Researcher notes
Do not generalize this to all Vite applications. The source bundle identifies exposed dev servers as the affected condition. Validate version, host exposure, and file-system deny behavior carefully. The provided evidence confirms fixed versions and KEV status, but not exploit telemetry or detailed attacker procedures.
Mitigation direction
- Upgrade Vite to 6.2.4, 6.1.3, 6.0.13, 5.4.16, 4.5.11, or later.
- Remove public or unnecessary network exposure for Vite development servers.
- Review Vite host configuration for intentional exposure only.
- Check vendor guidance for any newer remediation notes.
- Restrict developer tooling access to trusted networks only.
Validation and detection
- Inventory projects and lockfiles for affected Vite versions.
- Identify Vite dev servers reachable from untrusted networks.
- Review configuration for host settings exposing the dev server.
- Confirm upgraded versions in dependency manifests and resolved packages.
- Check logs or monitoring for suspicious access to dev-server file endpoints.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-31125 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N1.63.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/vitejs/vite/security/advisories/GHSA-4r4m-qw57-chr8CVE reference · x_refsource_CONFIRM
- https://github.com/vitejs/vite/commit/59673137c45ac2bcfad1170d954347c1a17ab949CVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-31125CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.