dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-57753

MEDIUM · 6.0 CVSS v4.0 Published 2025-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
vite-plugin-static-copy is rollup-plugin-copy for Vite with dev server support. Files not included in src are accessible with a crafted request. The vulnerability is fixed in 2.3.2 and 3.1.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vite-plugin-static-copy plugin, used to copy static files in Vite projects, has an access control vulnerability where files outside the intended src directory can be accessed through crafted HTTP requests. This allows unauthorized access to potentially sensitive files on the server.

MitigationUpgrade vite-plugin-static-copy to version 2.3.2 or 3.1.2 (depending on your major version) to patch the access control issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate vite-plugin-static-copy in project dependencies
    Check package.json for vite-plugin-static-copy under dependencies or devDependencies, or run 'npm list vite-plugin-static-copy' to see if it is installed
    Affected if The package is present in the project dependencies
  2. Identify the installed version
    Run 'npm list vite-plugin-static-copy' or check the version field in node_modules/vite-plugin-static-copy/package.json
    Affected if Version is less than 2.3.2 for v2.x releases OR less than 3.1.2 for v3.x releases
  3. Confirm the plugin is configured in Vite config
    Inspect vite.config.js, vite.config.ts, or similar config files for usage of 'viteStaticCopy' or import of the plugin
    Affected if The plugin is imported and configured in the Vite configuration file
  4. Check the src configuration
    Look for the 'files' or 'src' option in the viteStaticCopy configuration to identify which directories are being served
    Affected if The plugin is configured to serve any directories (this confirms the attack surface exists)
  5. Verify server exposure
    Confirm the Vite dev server or production server is accessible and the static copy files are being served via HTTP endpoints
    Affected if The server is running and serving files through this plugin

You are affected if vite-plugin-static-copy is installed, the version is below 2.3.2 or 3.1.2 depending on your major version, and the plugin is configured and serving files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade vite-plugin-static-copy to version 2.3.2 or 3.1.2 (depending on your major version) to patch the access control issue.

Recommended fix High confidence

vite-plugin-static-copy version 2.3.2 (for v2.x users) or 3.1.2 (for v3.x users)

  1. Identify your current major version of vite-plugin-static-copy (check package.json)
  2. If using version 2.x: Upgrade to version 2.3.2 or later by running: npm install [email protected]
  3. If using version 3.x: Upgrade to version 3.1.2 or later by running: npm install [email protected]
  4. Verify the upgrade completed successfully: npm list vite-plugin-static-copy
  5. Test your application to ensure the path traversal vulnerability is no longer present and functionality works as expected
Caveat Review the changelog between your current version and the target version for any breaking changes, particularly when crossing major version boundaries (e.g., v2 to v3)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57753 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57753 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data