/

CVE-2026-78037

Severity:

HIGH RISK

(8.8)

OS Command Injection (CWE-78) in Xiiaozet LK100W Device

CVE-2026-78037

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-78

Impact:

Privileged Command Execution and Device Compromise

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Xiiaozet LK100W contains an OS command injection vulnerability in its web-based management interface. An authenticated attacker may be able to execute arbitrary operating system commands with elevated privileges when attacker-controlled input reaches a system command without adequate separation or validation.

Affected context

The vulnerability occurs in the LK100W web management interface when an authenticated request can influence data used to construct or invoke an operating system command. Risk depends on the exposed management surface, the privileges assigned to the web service, and whether authorization and input-handling controls adequately constrain the affected operation.

Exploit preconditions

  • Attack surface: Web-based device management interface - Required access: Valid authenticated access, or another way to reach an

authenticated management session

  • Trigger point: A management operation that passes attacker-influenced data

to an operating system command

  • Why exploitation is possible: Input may be incorporated into a command

execution path without sufficient validation, escaping, or use of

argument-safe APIs; the service may execute the resulting command with

elevated privileges

Why this happens

The underlying bug is an OS command construction and execution flaw. The application treats externally influenced input as part of a command rather than as data passed through a constrained argument interface. This behavior maps to CWE-78, Improper Neutralization of Special Elements used in an OS Command, because command syntax may be interpreted by the operating system instead of being treated solely as input.

Potential impact

  • An attacker may execute arbitrary operating system commands.
  • Sensitive device or network information could be disclosed.
  • The web service account or a higher-privileged account could be abused.
  • Device configuration and security controls could be modified.
  • The device could be fully compromised or used to affect connected systems.

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from application workflows and reducing the trust placed in management-interface input. Common defensive patterns include using APIs that pass fixed executable names and discrete arguments without a shell, replacing free-form commands with allowlisted operations, applying strict type and range validation, and separating authorization checks from command construction. Management services can also run with the minimum required operating-system privileges, restrict administrative access to trusted networks, and isolate device control functions from sensitive system resources. These controls should be applied consistently to all equivalent request paths.

How teams detect issues like this

Detection approaches include static analysis for shell invocation APIs, string-based command construction, shell-evaluation features, and concatenation of request parameters into process arguments. Code reviews should examine authenticated management handlers, privilege boundaries, and whether allowlists and argument-safe interfaces are used. Runtime monitoring can alert on unexpected child processes, unusual command execution by the web service account, and administrative requests outside normal operational patterns. Automated security review tools and policy checks can help enforce restrictions on command execution in management components.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-239-01.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-239-01

Frequently asked

questions

It may be exploitable through the device's web-based management interface,

but exploitation generally requires authenticated access and network

reachability to that interface.

The stated condition is authenticated access to the management interface.

The practical scope depends on account permissions, interface exposure, and

any additional network or administrative controls.

Avoid shell-based command construction, use fixed allowlisted operations and

argument-safe process APIs, validate input by type and range, and run the

affected service with least privilege.

Treat all management-interface parameters as untrusted, enforce centralized

authorization, restrict administrative exposure, review command execution

paths, and monitor for unexpected processes launched by web services.

Find out what's already
exploitable in your codebase.