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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hxwc-5vw9-2w4w if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

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

NoSQL Injection in loopback-connector-mongodbGHSA-hxwc-5vw9-2w4w

GHSA-hxwc-5vw9-2w4w is a security vulnerability in loopback-connector-mongodb. A fix is available for loopback-connector-mongodb — see the affected versions and patch details below.

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

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.

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

loopback-connector-mongodbnpm

22Kdownloads / week

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`npm install loopback-connector-mongodb@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works