# CVE-2025-57685: Command injection in n/a

> Attackers can inject commands via the set_serial_cfg interface to gain root privileges and execute code on LB-Link routers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-8qv2-qrvw-2mg4

## What is CVE-2025-57685?

CVE-2025-57685 is a high-severity command injection vulnerability in n/a, published on 22 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The LB-Link routers, including the BL-AC2100_AZ3 V1.0.4, BL-WR4000 v2.5.0, BL-WR9000_AE4 v2.4.9, BL-AC1900_AZ2 v1.0.2, BL-X26_AC8 v1.2.8, and BL-LTE300_DA4 V1.2.3 models, are vulnerable to unauthorized command injection. Attackers can exploit this vulnerability by accessing the /goform/set_serial_cfg interface to gain the highest level of device privileges without authorization, enabling them to remotely execute malicious commands.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2025-57685 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57685 is a high-severity command injection vulnerability in n/a, published on 22 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57685 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-57685/ (Markdown: https://insights.sbomify.com/CVE-2025-57685/index.md)
```

## Sources

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

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