# CVE-2026-78037: Xiiaozet LK100W OS Command Injection

> An authenticated attacker can execute arbitrary OS commands on the Xiiaozet LK100W via its web interface, leading to device compromise.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-frm2-vmcc-vghq

## What is CVE-2026-78037?

CVE-2026-78037 is a high-severity command injection vulnerability in Xiiaozet LK100W, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Xiiaozet LK100W is vulnerable to OS command injection through its 
web-based management interface. An authenticated attacker may be able to
 execute arbitrary operating system commands with elevated privileges, 
potentially resulting in unauthorized access to sensitive information or
 complete device compromise.

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

## Which versions are affected by CVE-2026-78037?


## How do I fix CVE-2026-78037?

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

## Is CVE-2026-78037 being exploited?

There is no known exploitation of CVE-2026-78037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78037 and fix it if it is affected.

What it is: CVE-2026-78037 is a high-severity command injection vulnerability in Xiiaozet LK100W, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78037 in the wild and no public exploit code.

Affected product: Xiiaozet LK100W. 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-2026-78037/ (Markdown: https://insights.sbomify.com/CVE-2026-78037/index.md)
```

## Sources

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

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