dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-20001

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A vulnerability in the REST API of Cisco Secure FMC Software could allow an authenticated, remote attacker to conduct SQL injection attacks on an affected system. This vulnerability is due to inadequate validation of user-supplied input. An attacker could exploit this vulnerability by sending crafted requests to an affected device. A successful exploit could allow the attacker to obtain read access to the database and read certain files on the underlying operating system. To exploit this vulnerability, the attacker would need valid user credentials with any of the following roles: Administrator Security approver Access admin Network admin

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

SQL injection vulnerability in Cisco Secure FMC REST API allows authenticated attackers with specific roles (Administrator, Security approver, Access admin, Network admin) to inject malicious SQL commands through inadequately validated user-supplied input. Successful exploitation grants read access to the database and certain files on the underlying operating system.

MitigationApply Cisco's available patch/upgrade for FMC software; in the interim, limit the number of users granted Administrator, Security approver, Access admin, or Network admin roles to reduce attack surface, and monitor API traffic for anomalous SQL-like patterns.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 Cisco Secure FMC is deployed
    Identify if the system is running Cisco Firepower Management Center (FMC) by checking the product name/version via the web interface, CLI (show version), or API query to https://<fmc-host>/api/fdm/v2/flexconfig/about
    Affected if The system is not Cisco Secure FMC
  2. Check the FMC software version
    Access the FMC web interface and navigate to System > About > Updates, or use the CLI command 'show version' to obtain the installed version number
    Affected if The installed version falls within the vulnerable version range for this CVE (compare against Cisco's published affected versions)
  3. Verify REST API is enabled
    Check if the FMC REST API is enabled by navigating to System > Configuration > REST API Preferences in the web interface, or query the API endpoint /api/fdm/v1/featuregate to see if API access is granted
    Affected if REST API is enabled and accessible from the network
  4. Identify users with vulnerable roles
    Review user accounts and their assigned roles by navigating to System > Users > Users in the FMC web interface, or query the /api/fdm/v1/adminusers endpoint to list users with roles including Administrator, Security approver, Access admin, or Network admin
    Affected if Any user account possesses one of the roles: Administrator, Security approver, Access admin, or Network admin
  5. Review API access logs for SQL injection attempts
    Examine FMC logs under System > Diagnostics > Audit Log or via the /api/fdm/v1/audit/ endpoint, searching for SQL keywords (SELECT, UNION, INSERT, --, ';') in API request parameters that appear anomalous
    Affected if Recent audit logs show SQL-like patterns in API requests that could indicate exploitation attempts

A user is affected if they run a vulnerable version of Cisco Secure FMC with the REST API enabled and have any user accounts assigned Administrator, Security approver, Access admin, or Network admin roles.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco's available patch/upgrade for FMC software; in the interim, limit the number of users granted Administrator, Security approver, Access admin, or Network admin roles to reduce attack surface, and monitor API traffic for anomalous SQL-like patterns.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20001 — 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-20001 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