# CVE-2025-9580: LB-LINK BL-X26 HTTP set_blacklist os command injection

> Remote attackers can execute arbitrary OS commands via the mac argument in the set_blacklist handler of LB-LINK BL-X26 routers.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2025
- **Updated:** 28 Aug 2025
- **Also known as:** GHSA-6fg7-r75c-p826

## What is CVE-2025-9580?

CVE-2025-9580 is a medium-severity command injection vulnerability in LB-LINK BL-X26, published on 28 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in LB-LINK BL-X26 1.2.8. This affects an unknown function of the file /goform/set_blacklist of the component HTTP Handler. Such manipulation of the argument mac leads to os command injection. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Lb-Link Bl-X26 Firmware.

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

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

## Is CVE-2025-9580 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9580 is a medium-severity command injection vulnerability in LB-LINK BL-X26, published on 28 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9580 exists.

Affected product: LB-LINK BL-X26. 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-9580/ (Markdown: https://insights.sbomify.com/CVE-2025-9580/index.md)
```

## Sources

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

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