How severe is GHSA-cpgr-wmr9-qxv4?

No CVSS score has been assigned to GHSA-cpgr-wmr9-qxv4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cpgr-wmr9-qxv4?

GHSA-cpgr-wmr9-qxv4 affects the following packages: serve (npm). Ecosystems affected: npm.

How do I fix GHSA-cpgr-wmr9-qxv4?

Update serve to 10.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cpgr-wmr9-qxv4 is resolved across your whole dependency graph.

How do I detect GHSA-cpgr-wmr9-qxv4 in my npm dependencies?

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

How do I mitigate GHSA-cpgr-wmr9-qxv4 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-cpgr-wmr9-qxv4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cpgr-wmr9-qxv4 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.

When was GHSA-cpgr-wmr9-qxv4 published, and has it been updated?

GHSA-cpgr-wmr9-qxv4 was published on September 11, 2020 and was last updated on August 31, 2020. 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

Cross-Site Scripting in serveGHSA-cpgr-wmr9-qxv4

GHSA-cpgr-wmr9-qxv4 is a security vulnerability in serve. A fix is available for serve — see the affected versions and patch details below.

Published

Sep 11, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

servenpm

2.3Mdownloads / week

Description

Versions of serve prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.

Recommendation

Upgrade to version 10.0.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`serve`	all versions	10.0.2`npm install serve@10.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for serve, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update serve to 10.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cpgr-wmr9-qxv4 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Versions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code. ## Recommendation Upgrade to version 10.0.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-cpgr-wmr9-qxv4 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works