# CVE-2025-20306: Cisco Secure Firewall Management Center Software Command Injection Vulnerability

> Authenticated administrators can execute arbitrary root commands on Cisco FMC devices via crafted HTTP requests due to insufficient input validation.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-qf9j-hr2m-cp58

## What is CVE-2025-20306?

CVE-2025-20306 is a medium-severity command injection vulnerability in Cisco Secure Firewall Management Center, published on 14 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software could allow an authenticated, remote attacker with Administrator-level privileges to execute arbitrary commands on the underlying operating system.

This vulnerability is due to insufficient input validation of certain HTTP request parameters that are sent to the web-based management interface. An attacker could exploit this vulnerability by authenticating to the interface and sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to execute commands as the root user on the affected device. To exploit this vulnerability, an attacker would need Administrator-level credentials.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-20306?

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

## How do I fix CVE-2025-20306?

No fix has been published for CVE-2025-20306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20306 being exploited?

There is no known exploitation of CVE-2025-20306 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Secure Firewall Management Center

- [CVE-2026-20079](https://insights.sbomify.com/CVE-2026-20079/): Cisco Firewall Management Center Authentication Bypass Using an Alternate Path or Channel (critical 10.0, exploited in the wild)
- [CVE-2026-20131](https://insights.sbomify.com/CVE-2026-20131/): Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2026-20316](https://insights.sbomify.com/CVE-2026-20316/): Cisco Secure Firewall Management Center Use of Hard-coded Password (medium 5.3, exploited in the wild)
- [CVE-2025-20265](https://insights.sbomify.com/CVE-2025-20265/): Cisco Secure Firewall Management Center Software Radius Remote Code Execution Vulnerability (critical 10.0)
- [CVE-2024-20424](https://insights.sbomify.com/CVE-2024-20424/): Command injection in Cisco Firepower Management Center (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20306 and fix it if it is affected.

What it is: CVE-2025-20306 is a medium-severity command injection vulnerability in Cisco Secure Firewall Management Center, published on 14 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20306 in the wild and no public exploit code.

Affected product: Cisco Secure Firewall Management Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20306/ (Markdown: https://insights.sbomify.com/CVE-2025-20306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20306
- OSV: https://osv.dev/vulnerability/CVE-2025-20306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20306/
Summaries are generated and may contain mistakes; the official description above is the record.