dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-59509

CRITICAL · 9.2 CVSS v4.0 Published 2026-07-05
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An unauthenticated improper input validation vulnerability in the POST /fetch_cve_data endpoint in cve-search. A remote attacker can manipulate request parameters controlling the MongoDB collection, projected fields, and regular-expression filters to read arbitrary application MongoDB collections. This can expose administrative usernames and password hashes from the mgmt_users collection, enabling offline password cracking and potential administrative account compromise.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated MongoDB injection vulnerability in cve-search's POST /fetch_cve_data endpoint allows attackers to manipulate request parameters controlling MongoDB collection names, projected fields, and regex filters to read arbitrary database collections, including the mgmt_users collection containing admin username/password hashes.

MitigationImplement strict input validation on all request parameters, enforce authentication on the endpoint, and apply least-privilege database access controls to prevent unauthorized collection access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm cve-search installation and version
    Locate the cve-search application directory and check the version file or git commit history. Common paths include /opt/cve-search, /var/www/cve-search, or check via package manager if installed system-wide.
    Affected if The installed version does not include the patched input validation for the fetch_cve_data endpoint.
  2. Identify if POST /fetch_cve_data endpoint exists
    Review the application routing configuration (typically routes.py or app.py) and confirm the /fetch_cve_data endpoint is defined and accepts POST requests.
    Affected if The endpoint exists and is reachable without authentication.
  3. Check authentication enforcement on the endpoint
    Inspect the endpoint handler code to determine if authentication decorators or session validation are applied to the /fetch_cve_data route. Attempt a test request without credentials if safe to do so.
    Affected if The endpoint can be accessed without providing valid authentication credentials.
  4. Inspect parameter handling in the endpoint code
    Review the fetch_cve_data function to see how request parameters (collection, project, regex filters) are processed and passed to MongoDB queries. Look for direct string concatenation or unsafe query construction.
    Affected if User-supplied input from request parameters is used directly in MongoDB queries without sanitization.
  5. Verify input validation exists for MongoDB parameters
    Search the codebase for validation logic that sanitizes or restricts collection names, projected field names, and regex patterns before MongoDB query execution.
    Affected if No input validation or allowlist controls are implemented for the parameters controlling MongoDB collection names, projected fields, or regex filters.

You are affected if cve-search is installed, the /fetch_cve_data endpoint is exposed without authentication, and MongoDB query parameters are not validated or sanitized before being used in database operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Implement strict input validation on all request parameters, enforce authentication on the endpoint, and apply least-privilege database access controls to prevent unauthorized collection access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59509 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data