NoSQL Injection in loopback-connector-mongodb

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Versions of loopback-connector-mongodb before 3.6.0 are vulnerable to NoSQL injection. MongoDB Connector for LoopBack fails to properly sanitize a filter passed to query the database by allowing the dangerous $where property to be passed to the MongoDB Driver. The Driver allows the special $where property in a filter to execute JavaScript (client can pass in a malicious script) on the database Driver. This is an intended feature of MongoDB unless disabled (instructions here). A proof of concept malicious query: The above makes the database sleep for 5 seconds and then returns all “Posts” with the title containing the word Hello. Recommendation Update to version 3.6.0 or later.

Published by the source

4 Jun 2019, 19:36 UTC

Last modified by the source

9 Jan 2023, 05:01 UTC

Source last checked

26 Oct 2026, 12:06 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-m734-r4g6-34f9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-m734-r4g6-34f9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-m734-r4g6-34f9

Advisory: NoSQL Injection in loopback-connector-mongodb
IDs: GHSA-m734-r4g6-34f9
Record: https://patchnext.com/advisories/ghsa-m734-r4g6-34f9 (revision 2, source checked 26 Oct 2026, 12:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: loopback-connector-mongodb 3.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm loopback-connector-mongodb: affected < 3.6.0; fixed in 3.6.0

## Suggested inspection (read-only)
- `npm ls loopback-connector-mongodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on loopback-connector-mongodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m734-r4g6-34f9 (OSV record GHSA-m734-r4g6-34f9 lists affected ranges: npm loopback-connector-mongodb >=0 <3.6.0 (fixed))
- Verified: https://github.com/advisories/GHSA-m734-r4g6-34f9 (GitHub-reviewed advisory GHSA-m734-r4g6-34f9 lists affected ranges: npm loopback-connector-mongodb >=0 <3.6.0)

Commands are suggestions: review each one before running it.