# CVE-2022-20967: Cross-site scripting in Cisco Identity Services Engine Software

> Authenticated attackers can inject malicious scripts into the Cisco Identity Services Engine web interface, potentially compromising 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:** 18 Jan 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p2w9-mv5p-65w6

## What is CVE-2022-20967?

CVE-2022-20967 is a medium-severity cross-site scripting vulnerability in Cisco Identity Services Engine, published on 18 Jan 2023. 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 could allow an authenticated, remote attacker to conduct cross-site scripting attacks against other users of the application web-based management interface.

 This vulnerability is due to improper validation of input to an application feature before storage within the web-based management interface. An attacker could exploit this vulnerability by creating entries within the application interface that contain malicious HTML or script code. A successful exploit could allow the attacker to store malicious HTML or script code within the application interface for use in further cross-site scripting attacks.

 Cisco has not yet released software updates that address this vulnerability.

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

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

It affects 1 product.


Products: Cisco Identity Services Engine.

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

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

## Is CVE-2022-20967 being exploited?

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

What it is: CVE-2022-20967 is a medium-severity cross-site scripting vulnerability in Cisco Identity Services Engine, published on 18 Jan 2023. 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-20967 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-2022-20967/ (Markdown: https://insights.sbomify.com/CVE-2022-20967/index.md)
```

## Sources

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

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