How severe is GHSA-f5cv-xrv9-r8w7?

No CVSS score has been assigned to GHSA-f5cv-xrv9-r8w7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f5cv-xrv9-r8w7?

GHSA-f5cv-xrv9-r8w7 affects the following packages: express-cart (npm). Ecosystems affected: npm.

How do I fix GHSA-f5cv-xrv9-r8w7?

Update express-cart to 1.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5cv-xrv9-r8w7 is resolved across your whole dependency graph.

How do I detect GHSA-f5cv-xrv9-r8w7 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-f5cv-xrv9-r8w7 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-f5cv-xrv9-r8w7?

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

Is GHSA-f5cv-xrv9-r8w7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f5cv-xrv9-r8w7 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-f5cv-xrv9-r8w7 published, and has it been updated?

GHSA-f5cv-xrv9-r8w7 was published on September 1, 2020 and was last updated on September 24, 2021. 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-f5cv-xrv9-r8w7 — express-cart

GHSA-f5cv-xrv9-r8w7 is a security vulnerability in express-cart. A fix is available for express-cart — see the affected versions and patch details below.

NoSQL injection in express-cart

Published

Sep 1, 2020

Updated

Sep 24, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2021 · 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

70downloads / week

Description

Versions of express-cart before 1.1.8 are vulnerable to NoSQL injection.

The vulnerability is caused by the lack of user input sanitization in the login handlers. In both cases, the customer login and the admin login, parameters from the JSON body are sent directly into the MongoDB query which allows to insert operators.

These operators can be used to extract the value of the field blindly in the same manner of a blind SQL injection. In this case, the $regex operator is used to guess each character of the token from the start.

Recommendation

Update to version 1.1.8 or later.

Affected Packages

1 total 1 fixed

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

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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5cv-xrv9-r8w7 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-f5cv-xrv9-r8w7 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

Versions of `express-cart` before 1.1.8 are vulnerable to NoSQL injection. The vulnerability is caused by the lack of user input sanitization in the login handlers. In both cases, the customer login and the admin login, parameters from the JSON body are sent directly into the MongoDB query which allows to insert operators. These operators can be used to extract the value of the field blindly in the same manner of a blind SQL injection. In this case, the `$regex` operator is used to guess each character of the token from the start. ## Recommendation Update to version 1.1.8 or later.

O3 Security · Impact-Aware SCA

Is GHSA-f5cv-xrv9-r8w7 in your dependencies?

O3 Security finds GHSA-f5cv-xrv9-r8w7 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