How to fix: MongoDB $regex from user input
Building a MongoDB query with { field: { $regex: userInput } } or new RegExp(userInput) lets attackers supply patterns that match every document (.*) or trigger catastrophic backtracking, leaking data or causing DoS.
Why it matters
Wildcard or pathological regex patterns expose every document or stall the server.
The `code-sqli-mongodb-regex` check verifies that the server does not expose the `sqli-mongodb-regex` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Escape regex metacharacters before compiling user input with RegExp.
- 2Anchor patterns with ^ and bound their length; reject unbounded inputs.
- 3Prefer $text indexes over $regex for user-driven search.
Code examples
Escape or validate regex patterns from user input
// BAD: user controls the regex pattern, ReDoS possible
collection.find({ email: new RegExp(userInput) });
// GOOD: escape the user input before using as regex
function escapeRegex(s: string) { return s.replace(/[.*+?^${}()|[\]\\]/g, "\\$&"); }
collection.find({ email: new RegExp("^" + escapeRegex(userInput) + "$") });
// Or use a plain equality match instead of regexReferences
Detected automatically by VulnRadar. The check id is code-sqli-mongodb-regex, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is MongoDB $regex from user input?
- VulnRadar rates this medium severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-sqli-mongodb-regex, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does MongoDB $regex from user input map to?
- It maps to CWE-89. In the OWASP Top 10 it falls under A03:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.