How severe is GHSA-pp7p-q8fx-2968?

No CVSS score has been assigned to GHSA-pp7p-q8fx-2968 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pp7p-q8fx-2968?

GHSA-pp7p-q8fx-2968 affects the following packages: vite-plugin-static-copy (npm), vite-plugin-static-copy (npm). Ecosystems affected: npm.

How do I fix GHSA-pp7p-q8fx-2968?

Update vite-plugin-static-copy to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pp7p-q8fx-2968 is resolved across your whole dependency graph.

How do I detect GHSA-pp7p-q8fx-2968 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vite-plugin-static-copy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pp7p-q8fx-2968 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pp7p-q8fx-2968?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pp7p-q8fx-2968 can be triaged on real exposure rather than presence alone.

Is GHSA-pp7p-q8fx-2968 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pp7p-q8fx-2968 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pp7p-q8fx-2968?

GHSA-pp7p-q8fx-2968 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pp7p-q8fx-2968?

GHSA-pp7p-q8fx-2968 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-pp7p-q8fx-2968 published, and has it been updated?

GHSA-pp7p-q8fx-2968 was published on August 21, 2025 and was last updated on August 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-pp7p-q8fx-2968 — vite-plugin-static-copy

Fix: sapphi-red/vite-plugin-static-copy@0bc6b49

GHSA-pp7p-q8fx-2968 is a Path Traversal vulnerability in vite-plugin-static-copy. A fix is available for vite-plugin-static-copy — see the affected versions and patch details below.

vite-plugin-static-copy files not included in `src` are possible to access with a crafted request

Also known asCVE-2025-57753

Published

Aug 21, 2025

Updated

Aug 21, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pp7p-q8fx-2968.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

201other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

vite-plugin-static-copynpm

1.4Mdownloads / week

Description

Summary

Files not included in src was possible to access with a crafted request.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.

Arbitrary files can be disclosed by exploiting this vulnerability.

Details

Consider the following configuration in used by vite.config.ts:

import { defineConfig } from 'vite'
import { viteStaticCopy } from 'vite-plugin-static-copy'

export default defineConfig({
    plugins: [
      viteStaticCopy({
        targets: [
          {
            src: "./public/images",
            dest: "./",
          },
        ],
      }),
    ],
  });

The files under the ./public/images is only expected to be served. Abusing this vulnerability, an attacker can access arbitrary files on the filesystem.

PoC

I've attached a demo app to showcase the bug.

Run it with npm run dev and issue the following HTTP request

GET /static/images/../../../../../../../etc/passwd HTTP/1.1
Host: localhost:3001
Content-Length: 2

curl --path-as-is -i -s -k -X $'GET' \
    -H $'Host: localhost:3001' -H $'Content-Length: 2' \
    --data-binary $'\x0d\x0a' \
    $'http://localhost:3001/static/images/../../../../../../../etc/passwd'

Observe that the /etc/passwd file is included in the response.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vite-plugin-static-copy`	≥ 3.0.0&&< 3.1.2	3.1.2`npm install vite-plugin-static-copy@3.1.2`
📦npm	`vite-plugin-static-copy`	≥ 0.4.3&&< 2.3.2	2.3.2`npm install vite-plugin-static-copy@2.3.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vite-plugin-static-copy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vite-plugin-static-copy to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pp7p-q8fx-2968 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pp7p-q8fx-2968 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pp7p-q8fx-2968. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Files not included in `src` was possible to access with a crafted request. ### Impact Only apps explicitly exposing the Vite dev server to the network (using --host or [server.host config option](https://vitejs.dev/config/server-options.html#server-host)) are affected. Arbitrary files can be disclosed by exploiting this vulnerability. ### Details Consider the following configuration in used by `vite.config.ts`: ```ts import { defineConfig } from 'vite' import { viteStaticCopy } from 'vite-plugin-static-copy' export default defineConfig({ plugins: [ viteStaticCopy(

O3 Security · Impact-Aware SCA

Is GHSA-pp7p-q8fx-2968 in your dependencies?

O3 Security finds GHSA-pp7p-q8fx-2968 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works