# CVE-2019-15268: Cisco Firepower Management Center Multiple Cross-Site Scripting Vulnerabilities

> Authenticated attackers can execute arbitrary scripts or access sensitive data via XSS in the Cisco FMC web interface.

- **Severity:** Medium 4.8 (`CVSS:3.0/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:** 16 Oct 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-x353-6pcq-w9gj

## What is CVE-2019-15268?

CVE-2019-15268 is a medium-severity cross-site scripting vulnerability in Cisco Firepower Management Center, published on 16 Oct 2019. 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) could allow an authenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based management interface. These vulnerabilities are due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit these vulnerabilities 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 access sensitive, browser-based information.

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

## Which versions are affected by CVE-2019-15268?

It affects 34 products.


Products: Cisco Amp 7150 Firmware, Cisco Amp 8150 Firmware, Cisco Firepower Appliance 7010 Firmware, Cisco Firepower Appliance 7020 Firmware, Cisco Firepower Appliance 7030 Firmware, Cisco Firepower Appliance 7050 Firmware, Cisco Firepower Appliance 7110 Firmware, Cisco Firepower Appliance 7115 Firmware, Cisco Firepower Appliance 7120 Firmware, Cisco Firepower Appliance 7125 Firmware, Cisco Firepower Appliance 8120 Firmware, Cisco Firepower Appliance 8130 Firmware, Cisco Firepower Appliance 8140 Firmware, Cisco Firepower Appliance 8250 Firmware, Cisco Firepower Appliance 8260 Firmware, Cisco Firepower Appliance 8270 Firmware, Cisco Firepower Appliance 8290 Firmware, Cisco Firepower Appliance 8350 Firmware, Cisco Firepower Appliance 8360 Firmware, Cisco Firepower Appliance 8370 Firmware and 14 more.

## How do I fix CVE-2019-15268?

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

## Is CVE-2019-15268 being exploited?

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

## Other vulnerabilities in Cisco Firepower Management Center

- [CVE-2018-0365](https://insights.sbomify.com/CVE-2018-0365/): Cross-site request forgery in Cisco Firepower Management Center unknown (high 8.8)
- [CVE-2019-15269](https://insights.sbomify.com/CVE-2019-15269/): Cisco Firepower Management Center Multiple Cross-Site Scripting Vulnerabilities (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15268 and fix it if it is affected.

What it is: CVE-2019-15268 is a medium-severity cross-site scripting vulnerability in Cisco Firepower Management Center, published on 16 Oct 2019. 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-2019-15268 in the wild and no public exploit code.

Affected product: Cisco Firepower 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-2019-15268/ (Markdown: https://insights.sbomify.com/CVE-2019-15268/index.md)
```

## Sources

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

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