# CVE-2022-20839: Cross-site scripting in Cisco Firepower Management Center

> Authenticated attackers can inject malicious scripts into the Cisco FMC web interface, enabling arbitrary code execution or data theft against other users.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8jjw-2j6j-mwc7

## What is CVE-2022-20839?

CVE-2022-20839 is a medium-severity cross-site scripting vulnerability in Cisco Secure Firewall Management Center, published on 10 Nov 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple vulnerabilities in the web-based management interface of Cisco Firepower Management Center (FMC) Software could allow an authenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface of an affected device.
     
These vulnerabilities are due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit these vulnerabilities by inserting crafted input into various data fields in an affected interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface, or access sensitive, browser-based information. In some cases, it is also possible to cause a temporary availability impact to portions of the FMC Dashboard.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-20839?

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

## How do I fix CVE-2022-20839?

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

## Is CVE-2022-20839 being exploited?

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

What it is: CVE-2022-20839 is a medium-severity cross-site scripting vulnerability in Cisco Secure Firewall Management Center, published on 10 Nov 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-20839 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-2022-20839/ (Markdown: https://insights.sbomify.com/CVE-2022-20839/index.md)
```

## Sources

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

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