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

> Unauthenticated attackers can inject arbitrary JavaScript into the router's web interface via the cmd parameter, requiring user interaction to execute.

- **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:** 31 Jul 2025
- **Updated:** 31 Jul 2025
- **Also known as:** GHSA-gcm8-8cp3-3x4h

## What is CVE-2025-51569?

CVE-2025-51569 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Jul 2025. 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 cross-site scripting (XSS) vulnerability exists in the LB-Link BL-CPE300M 01.01.02P42U14_06 router's web interface. The /goform/goform_get_cmd_process endpoint fails to sanitize user input in the cmd parameter before reflecting it into a text/html response. This allows unauthenticated attackers to inject arbitrary JavaScript, which is executed in the context of the router's origin when the crafted URL is accessed. The issue requires user interaction to exploit.

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

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


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

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

## Is CVE-2025-51569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51569 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Jul 2025. 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-51569 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-51569/ (Markdown: https://insights.sbomify.com/CVE-2025-51569/index.md)
```

## Sources

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

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