Skip to main content
HighContentOWASP A05:2021CWE-209

How to fix: NoSQL Error Message Exposed

NoSQL/MongoDB error found in response.

Why it matters

Reveals database type and query structure.

NoSQL errors aid injection attacks.

How to fix it

  1. 1Use custom error pages, handle errors gracefully.

Code examples

Catch and mask NoSQL errors

TypeScript
try {
  const result = await db.collection.findOne({ _id: id });
  return Response.json(result);
} catch (err) {
  console.error("MongoDB error:", err); // log server-side only
  return Response.json({ error: "Database error" }, { status: 500 });
  // Never expose: MongoServerError, collection names, or query details
}

References

Detected automatically by VulnRadar. The check id is nosql-error-exposed, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is NoSQL Error Message Exposed?
VulnRadar rates this high severity in the content 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 nosql-error-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does NoSQL Error Message Exposed map to?
It maps to CWE-209. In the OWASP Top 10 it falls under A05: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.

Propose a checkHow a check is built

Scan your own site for nosql error message exposed

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs