Skip to main content
CVE-2025-20301VulnerabilityPublished

CVE-2025-20301: Cisco Firepower Management Center · Missing Authorization

Affects Cisco Firepower Management CenterSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Cisco Cisco Firepower Management CenterAffected
  • =6.2.3.12
  • =6.2.3.1
  • =6.2.3.10
  • =6.2.3.8
  • =6.4.0.6
  • =6.2.3
  • =6.4.0.7
  • =6.2.3.13
  • =6.2.3.5
  • =6.4.0.4
  • =6.2.3.9
  • =6.2.3.14
  • =6.4.0.1
  • =6.2.3.6
  • =6.2.3.11
  • =6.4.0.8
  • =6.2.3.2
  • =6.4.0.2
  • =6.2.3.3
  • =6.4.0.3
  • =6.2.3.7
  • =6.2.3.4
  • =6.4.0.5
  • =6.4.0
  • =6.2.3.15
  • =6.6.0
  • =6.4.0.9
  • =6.2.3.16
  • =6.6.0.1
  • =6.6.1
  • =6.4.0.10
  • =6.4.0.11
  • =6.6.3
  • =6.6.4
  • =6.4.0.12
  • =7.0.0
  • =6.2.3.17
  • =7.0.0.1
  • =6.6.5
  • =7.0.1
  • =7.1.0
  • =6.6.5.1
  • =6.4.0.13
  • =7.0.1.1
  • =6.2.3.18
  • =6.4.0.14
  • =6.6.5.2
  • =7.1.0.1
  • =7.0.2
  • =6.4.0.15
  • =7.2.0
  • =7.0.2.1
  • =7.0.3
  • =6.6.7
  • =7.1.0.2
  • =7.2.0.1
  • =7.0.4
  • =7.2.1
  • =7.0.5
  • =6.4.0.16
  • =7.3.0
  • =7.2.2
  • =6.6.7.1
  • =7.3.1
  • =7.2.3
  • =7.1.0.3
  • =7.2.3.1
  • =7.2.4
  • =7.0.6
  • =7.2.4.1
  • =7.2.5
  • =7.3.1.1
  • =7.4.0
  • =6.4.0.17
  • =7.0.6.1
  • =7.2.5.1
  • =7.4.1
  • =7.2.6
  • =7.4.1.1
  • =7.0.6.2
  • =6.4.0.18
  • =6.6.7.2
  • =7.2.7
  • =7.2.5.2
  • =7.3.1.2
  • =7.2.8
  • =7.6.0
  • =7.4.2
  • =7.2.8.1
  • =7.0.6.3
  • =7.4.2.1
  • =7.2.9
  • =7.0.7
Fixed in–

AI-suggested

1. Immediate patching: Organizations should prioritize applying Cisco’s security updates or patches addressing CVE-2025-20301 as soon as they become available. 2. Access control review: Restrict access to the FMC management interface to only trusted administrators and enforce strict role-based access controls to minimize the number of users with any level of access. 3. Network segmentation: Isolate the FMC management network segment from general user networks and limit access via VPN or jump hosts with multi-factor authentication. 4. Monitoring and logging: Enable detailed logging of access to troubleshoot files and regularly audit logs for unusual access patterns or attempts to access cross-domain data. 5. Temporary workarounds: Until patches are applied, consider disabling or restricting access to troubleshoot file retrieval features if feasible. 6. User training: Educate administrators about the risk of using low-privileged accounts and the importance of safeguarding credentials to prevent misuse. 7. Incident response readiness: Prepare to investigate and respond promptly to any signs of exploitation or suspicious activity related to FMC access.

Description

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.

References

Community reviews

Loading reviews…