# CVE-2025-5516: TOTOLINK X2000R URL Filtering Page formFilter cross site scripting

> Remote attackers can inject malicious scripts via the URL filtering page, potentially compromising user sessions on TOTOLINK X2000R routers.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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:** 3 Jun 2025
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-r8gp-c62w-m7jr

## What is CVE-2025-5516?

CVE-2025-5516 is a medium-severity cross-site scripting vulnerability in TOTOLINK X2000R, published on 3 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in TOTOLINK X2000R 1.0.0-B20230726.1108. This affects an unknown part of the file /boafrm/formFilter of the component URL Filtering Page. The manipulation of the argument URL Address leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Totolink X2000r Firmware.

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

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

## Is CVE-2025-5516 being exploited?

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

## Other vulnerabilities in TOTOLINK X2000R

- [CVE-2024-22529](https://insights.sbomify.com/CVE-2024-22529/): Command injection in n/a (critical 9.8)
- [CVE-2023-51133](https://insights.sbomify.com/CVE-2023-51133/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-51135](https://insights.sbomify.com/CVE-2023-51135/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-51136](https://insights.sbomify.com/CVE-2023-51136/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-46545](https://insights.sbomify.com/CVE-2023-46545/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5516 is a medium-severity cross-site scripting vulnerability in TOTOLINK X2000R, published on 3 Jun 2025. An attacker needs administrator access to exploit it, 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-5516 exists.

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

## Sources

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

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