How severe is GHSA-hxwc-5vw9-2w4w?

No CVSS score has been assigned to GHSA-hxwc-5vw9-2w4w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hxwc-5vw9-2w4w?

GHSA-hxwc-5vw9-2w4w affects the following packages: loopback-connector-mongodb (npm). Ecosystems affected: npm.

How do I fix GHSA-hxwc-5vw9-2w4w?

Update loopback-connector-mongodb to 3.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxwc-5vw9-2w4w is resolved across your whole dependency graph.

How do I detect GHSA-hxwc-5vw9-2w4w in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loopback-connector-mongodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hxwc-5vw9-2w4w 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-hxwc-5vw9-2w4w?

O3 pinpoints whether GHSA-hxwc-5vw9-2w4w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hxwc-5vw9-2w4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-hxwc-5vw9-2w4w 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-hxwc-5vw9-2w4w published, and has it been updated?

GHSA-hxwc-5vw9-2w4w was published on September 2, 2020 and was last updated on September 27, 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-hxwc-5vw9-2w4w

GHSA-hxwc-5vw9-2w4w is a security vulnerability in loopback-connector-mongodb. O3 Security confirms whether GHSA-hxwc-5vw9-2w4w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

NoSQL Injection in loopback-connector-mongodb

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦loopback-connector-mongodb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Versions of loopback-connector-mongodb prior to 3.6.0 are vulnerable to NoSQL Injection. Filters passed to the database query are not properly sanitized which leads to execution of code on the database driver and data leak.

Recommendation

Upgrade to version 3.6.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`loopback-connector-mongodb`	all versions	3.6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loopback-connector-mongodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update loopback-connector-mongodb to 3.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxwc-5vw9-2w4w 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 pinpoints whether GHSA-hxwc-5vw9-2w4w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hxwc-5vw9-2w4w. 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 `loopback-connector-mongodb` prior to 3.6.0 are vulnerable to NoSQL Injection. Filters passed to the database query are not properly sanitized which leads to execution of code on the database driver and data leak. ## Recommendation Upgrade to version 3.6.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-hxwc-5vw9-2w4w in your dependencies?

O3 detects GHSA-hxwc-5vw9-2w4w across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works