# CVE-2017-12220: Cross-site scripting in Cisco Firepower Management Center

> Unauthenticated attackers can execute arbitrary scripts or access sensitive data via reflected XSS in the Cisco Firepower Management Center web interface.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-68gc-f3v5-qx9r

## What is CVE-2017-12220?

CVE-2017-12220 is a medium-severity cross-site scripting vulnerability in Cisco Secure Firewall Management Center, published on 7 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco Firepower Management Center could allow an unauthenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information. Cisco Bug IDs: CSCvc50771.

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

## Which versions are affected by CVE-2017-12220?

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

## How do I fix CVE-2017-12220?

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

## Is CVE-2017-12220 being exploited?

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

What it is: CVE-2017-12220 is a medium-severity cross-site scripting vulnerability in Cisco Secure Firewall Management Center, published on 7 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-12220 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-2017-12220/ (Markdown: https://insights.sbomify.com/CVE-2017-12220/index.md)
```

## Sources

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

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