# CVE-2022-23137: Cross-site scripting in ZXCDN

> Attackers can execute arbitrary scripts in users' browsers via a crafted URL in ZTE ZXCDN, potentially leading to session hijacking or data theft.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 11 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-96p5-93ww-4wgg

## What is CVE-2022-23137?

CVE-2022-23137 is a medium-severity cross-site scripting vulnerability in ZXCDN, published on 11 May 2022. 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

ZTE's ZXCDN product has a reflective XSS vulnerability. The attacker could modify the parameters in the content clearing request url, and when a user clicks the url, an XSS attack will be triggered.

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

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

It affects 1 product.


Products: Zte Zxcdn Firmware.

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

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

## Is CVE-2022-23137 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23137 and fix it if it is affected.

What it is: CVE-2022-23137 is a medium-severity cross-site scripting vulnerability in ZXCDN, published on 11 May 2022. 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-2022-23137 in the wild and no public exploit code.

Affected product: ZXCDN. 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-23137/ (Markdown: https://insights.sbomify.com/CVE-2022-23137/index.md)
```

## Sources

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

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