# CVE-2023-20030: Cisco Identity Services Engine XML External Entity Injection Vulnerability

> Authenticated attackers can exploit XXE in Cisco ISE to read local files, perform SSRF, or cause denial of service.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2023
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-25m5-5hwm-rp7r

## What is CVE-2023-20030?

CVE-2023-20030 is a medium-severity vulnerability in Cisco Identity Services Engine, published on 5 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to access sensitive information, conduct a server-side request forgery (SSRF) attack through an affected device, or negatively impact the responsiveness of the web-based management interface itself. This vulnerability is due to improper handling of XML External Entity (XXE) entries when parsing certain XML files. An attacker could exploit this vulnerability by uploading a crafted XML file that contains references to external entities. A successful exploit could allow the attacker to retrieve files from the local system, resulting in the disclosure of confidential information. A successful exploit could also cause the web application to perform arbitrary HTTP requests on behalf of the attacker or consume memory resources to reduce the availability of the web-based management interface. To successfully exploit this vulnerability, an attacker would need valid Super Admin or Policy Admin credentials.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2023-20030?

It affects 1 product.


Products: Cisco Identity Services Engine.

## How do I fix CVE-2023-20030?

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

## Is CVE-2023-20030 being exploited?

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

What it is: CVE-2023-20030 is a medium-severity vulnerability in Cisco Identity Services Engine, published on 5 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-20030 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-2023-20030/ (Markdown: https://insights.sbomify.com/CVE-2023-20030/index.md)
```

## Sources

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

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