dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2025-20301

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-14
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 web-based management interface of Cisco Secure FMC Software could allow an authenticated, low-privileged, remote attacker to access troubleshoot files for a different domain. This vulnerability is due to missing authorization checks. An attacker could exploit this vulnerability by directly accessing a troubleshoot file for a different domain that is managed on the same Cisco Secure FMC instance. A successful exploit could allow the attacker to retrieve a troubleshoot file for a different domain, which could allow the attacker to access sensitive information contained in the troubleshoot file.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in Cisco Secure FMC's web-based management interface. An authenticated, low-privileged remote attacker can directly access troubleshoot files for domains they don't manage on the same FMC instance because the application lacks proper authorization checks before serving these files. Successful exploitation exposes sensitive information contained in troubleshoot logs from other domains.

MitigationApply Cisco's patch for CVE-2025-20301 when released. In the interim, strictly limit FMC administrative access to trusted personnel and consider network segmentation to reduce attack surface.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Secure Firewall Management CenterApplication
Affected:= 6.2.3= 6.2.3.1= 6.2.3.2= 6.2.3.3= 6.2.3.4= 6.2.3.5= 6.2.3.6= 6.2.3.7= 6.2.3.8= 6.2.3.9= 6.2.3.10= 6.2.3.11

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. Identify Cisco FMC version
    Log into the FMC web interface and navigate to System > About > Cisco Firepower Management Center, or run 'show version' via CLI. Look for the exact version number in the format 6.2.3.x.
    Affected if The installed version is 6.2.3, 6.2.3.1, 6.2.3.2, 6.2.3.3, 6.2.3.4, 6.2.3.5, 6.2.3.6, 6.2.3.7, 6.2.3.8, 6.2.3.9, 6.2.3.10, or 6.2.3.11.
  2. Verify FMC web interface is enabled
    Check if the FMC web-based management interface (HTTPS on port 443 or configured port) is accessible and active. This is typically enabled by default on FMC appliances.
    Affected if The FMC web interface is reachable from the network where untrusted users could connect.
  3. Confirm multi-domain configuration
    In the FMC web interface, navigate to System > Domains or check the domain structure. Determine if more than one domain is configured on the same FMC instance.
    Affected if Multiple domains are configured on a single FMC instance, as the vulnerability allows cross-domain access to troubleshoot files.
  4. Review user role assignments
    In the FMC web interface, navigate to System > Users > Users or System > Users > User Roles. Identify users with standard or read-only access who are assigned to specific domains.
    Affected if Low-privileged users exist who have access to only some domains but not others on a multi-domain FMC.

You are affected if your FMC runs version 6.2.3.x (any patch from 6.2.3 through 6.2.3.11), has the web interface enabled, uses multiple domains, and has users with domain-restricted access.

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 patch for CVE-2025-20301 when released. In the interim, strictly limit FMC administrative access to trusted personnel and consider network segmentation to reduce attack surface.

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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