# CVE-2023-26801: Command injection in n/a

> Attackers can execute arbitrary commands on LB-LINK routers via the set_LimitClient_cfg endpoint, potentially compromising the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2023
- **Updated:** 5 May 2025
- **Also known as:** GHSA-c5pj-m2vw-68wh

## What is CVE-2023-26801?

CVE-2023-26801 is a critical command injection vulnerability in n/a, published on 26 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LB-LINK BL-AC1900_2.0 v1.0.1, LB-LINK BL-WR9000 v2.4.9, LB-LINK BL-X26 v1.2.5, and LB-LINK BL-LTE300 v1.0.8 were discovered to contain a command injection vulnerability via the mac, time1, and time2 parameters at /goform/set_LimitClient_cfg.

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

## Which versions are affected by CVE-2023-26801?

It affects 4 products.


Products: Lb-Link Bl-Ac1900 Firmware, Lb-Link Bl-Lte300 Firmware, Lb-Link Bl-Wr9000 Firmware, Lb-Link Bl-X26 Firmware.

## How do I fix CVE-2023-26801?

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

## Is CVE-2023-26801 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26801 and fix it if it is affected.

What it is: CVE-2023-26801 is a critical command injection vulnerability in n/a, published on 26 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26801 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-2023-26801/ (Markdown: https://insights.sbomify.com/CVE-2023-26801/index.md)
```

## Sources

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

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