# CVE-2022-23136: Cross-site scripting in ZXHN F680

> Attackers can inject malicious scripts via gateway name modification, leading to XSS attacks when users view the device topology.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2w7c-p47h-jm95

## What is CVE-2022-23136?

CVE-2022-23136 is a medium-severity cross-site scripting vulnerability in ZXHN F680, published on 30 Mar 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

There is a stored XSS vulnerability in ZTE home gateway product. An attacker could modify the gateway name by inserting special characters and trigger an XSS attack when the user views the current topology of the device through the management page.

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

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

It affects 1 product.


Products: Zte Zxhn F680 Firmware.

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

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

## Is CVE-2022-23136 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23136 is a medium-severity cross-site scripting vulnerability in ZXHN F680, published on 30 Mar 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23136 in the wild and no public exploit code.

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

## Sources

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

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