How severe is GHSA-8h8v-6qqm-fwpq?

No CVSS score has been assigned to GHSA-8h8v-6qqm-fwpq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8h8v-6qqm-fwpq?

GHSA-8h8v-6qqm-fwpq affects the following packages: express-cart (npm). Ecosystems affected: npm.

How do I fix GHSA-8h8v-6qqm-fwpq?

Update express-cart to 1.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8h8v-6qqm-fwpq is resolved across your whole dependency graph.

How do I detect GHSA-8h8v-6qqm-fwpq in my npm dependencies?

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

How do I mitigate GHSA-8h8v-6qqm-fwpq if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-8h8v-6qqm-fwpq actively exploited in the wild?

No public exploit code has been indexed for GHSA-8h8v-6qqm-fwpq 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-8h8v-6qqm-fwpq published, and has it been updated?

GHSA-8h8v-6qqm-fwpq was published on September 1, 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

Path Traversal in express-cartGHSA-8h8v-6qqm-fwpq

GHSA-8h8v-6qqm-fwpq is a security vulnerability in express-cart. A fix is available for express-cart — see the affected versions and patch details below.

Published

Sep 1, 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.

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

express-cartnpm

107downloads / week

Description

Versions of express-cart before 1.1.7 are vulnerable to Path Traversal.

Recommendation

Update to version 1.1.7 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`express-cart`	all versions	1.1.7`npm install express-cart@1.1.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for express-cart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update express-cart to 1.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8h8v-6qqm-fwpq is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Versions of `express-cart` before 1.1.7 are vulnerable to Path Traversal. ## Recommendation Update to version 1.1.7 or later.

O3 Security · Impact-Aware SCA

Is GHSA-8h8v-6qqm-fwpq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works