# CVE-2025-70545: Cross-site scripting in n/a

> Remote unauthenticated attackers can inject persistent JavaScript into the router's web interface, potentially leading to session hijacking or malicious actions.

- **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:** 4 Feb 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-m7x2-xj86-v5cr

## What is CVE-2025-70545?

CVE-2025-70545 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2026. 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

A stored cross-site scripting (XSS) vulnerability exists in the web management interface of the PPC (Belden) ONT 2K05X router running firmware v1.1.9_206L. The Common Gateway Interface (CGI) component improperly handles user-supplied input, allowing a remote, unauthenticated attacker to inject arbitrary JavaScript that is persistently stored and executed when the affected interface is accessed.

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

## Which versions are affected by CVE-2025-70545?

It affects 1 product.


Products: Belden Ppc 2k05x Firmware.

## How do I fix CVE-2025-70545?

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

## Is CVE-2025-70545 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70545 exists.

Public exploit code:

- https://github.com/jeyabalaji711/CVE-2025-70545 (github_poc): https://github.com/jeyabalaji711/CVE-2025-70545

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70545 and fix it if it is affected.

What it is: CVE-2025-70545 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70545 exists.

Affected product: n/a. 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-2025-70545/ (Markdown: https://insights.sbomify.com/CVE-2025-70545/index.md)
```

## Sources

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

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