# CVE-2025-20148: Cisco Secure Firewall Management Center HTML Injection Vulnerability

> Authenticated attackers can inject HTML to read files and perform SSRF in Cisco Secure Firewall Management Center.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 14 Aug 2025
- **Also known as:** GHSA-wx6g-rg4g-cr55

## What is CVE-2025-20148?

CVE-2025-20148 is a high-severity cross-site scripting vulnerability in Cisco Secure Firewall Management Center, published on 14 Aug 2025. Any signed-in user can exploit it over the network, 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 to inject arbitrary HTML content into a device-generated document.

This vulnerability is due to improper validation of user-supplied data. An attacker could exploit this vulnerability by submitting malicious content to an affected device and using the device to generate a document that contains sensitive information. A successful exploit could allow the attacker to alter the standard layout of the device-generated documents, read arbitrary files from the underlying operating system, and conduct server-side request forgery (SSRF) attacks. To exploit this vulnerability, the attacker must have valid credentials for a user account with at least the role of Security Analyst (Read Only).

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

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

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

## Is CVE-2025-20148 being exploited?

There is no known exploitation of CVE-2025-20148 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-20148 and fix it if it is affected.

What it is: CVE-2025-20148 is a high-severity cross-site scripting vulnerability in Cisco Secure Firewall Management Center, published on 14 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20148 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-20148/ (Markdown: https://insights.sbomify.com/CVE-2025-20148/index.md)
```

## Sources

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

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