# CVE-2026-20047: Cisco Identity Services Engine Cross-Site Scripting Vulnerability

> An authenticated attacker can inject malicious scripts into the Cisco ISE web interface to execute code or steal browser data.

- **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:** 15 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-vgf7-qrg3-cm45

## What is CVE-2026-20047?

CVE-2026-20047 is a medium-severity cross-site scripting vulnerability in Cisco Identity Services Engine, published on 15 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) could allow an authenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the interface.

This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected system. An attacker could exploit this vulnerability by injecting malicious code into specific pages of the interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. To exploit this vulnerability, the attacker must have valid administrative credentials.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2026-20047?

It affects 1 product.


Products: Cisco Identity Services Engine.

## How do I fix CVE-2026-20047?

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

## Is CVE-2026-20047 being exploited?

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

## Other vulnerabilities in Cisco Identity Services Engine

- [CVE-2026-76460](https://insights.sbomify.com/CVE-2026-76460/): Cisco Identity Services Engine Incorrect Use of Privileged APIs (critical 10.0, exploited in the wild)
- [CVE-2025-20337](https://insights.sbomify.com/CVE-2025-20337/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2025-20281](https://insights.sbomify.com/CVE-2025-20281/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2026-20130](https://insights.sbomify.com/CVE-2026-20130/): Cisco Identity Services Engine Hardening Release - Improper Neutralization Vulnerabilities (critical 10.0)
- [CVE-2026-20192](https://insights.sbomify.com/CVE-2026-20192/): Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20047 and fix it if it is affected.

What it is: CVE-2026-20047 is a medium-severity cross-site scripting vulnerability in Cisco Identity Services Engine, published on 15 Jan 2026. 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-2026-20047 in the wild and no public exploit code.

Affected product: Cisco Identity Services Engine. 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-2026-20047/ (Markdown: https://insights.sbomify.com/CVE-2026-20047/index.md)
```

## Sources

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

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