/

CVE-2026-75161

Severity:

HIGH RISK

(8.8)

OS Command Injection (CWE-77) in X-Serie Gateway Firmware

CVE-2026-75161

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77

Impact:

Privileged Remote Code Execution

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

A command injection vulnerability in the MBS-Solutions X-Serie Gateway allows an authenticated user with the low-privileged Standard role to influence commands executed by the gateway's restart functionality.

Under the affected firmware conditions, this may enable arbitrary code execution with root privileges through the dpcheck system utility.

Affected context

The issue occurs in the ugw-restart method of /cgi-bin/wwwugw.cgi in X-Serie Gateway firmware V6_00_05. It becomes risky when attacker-controlled request data reaches the restart workflow and is incorporated into a system utility invocation without sufficient command or argument isolation. Exploitation requires access to the gateway's authenticated web interface with the Standard role.

Exploit preconditions

  • Attack surface: Authenticated web interface exposed through /cgi-bin/wwwugw.cgi
  • Required access: A valid account with the low-privileged Standard role
  • Trigger point: The ugw-restart method and its invocation of the dpcheck system utility
  • Why exploitation is possible: Insufficient separation between user-controlled input and operating-system command execution may allow injected command content to be interpreted by a root-owned process

Why this happens

The vulnerability reflects OS command injection, mapped to CWE-77, where externally influenced input is incorporated into a command executed by the operating system without robust separation between data and executable syntax. The insecure pattern may involve shell-based command construction, inadequate argument validation, or failure to use a parameterized process execution interface. Because the affected utility runs with root privileges, successful command interpretation can cross the intended authorization boundary.

Potential impact

  • An attacker may execute arbitrary commands on the gateway
  • Compromise could occur with root-level privileges
  • Device configuration and security controls could be altered
  • Sensitive gateway, network, or service information could be exposed
  • The gateway could be used for persistence, disruption, or further network access

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from privileged workflows and treating all request-derived values as untrusted.

Common defensive patterns include:

  • Using parameterized process-execution APIs rather than concatenated shell commands
  • Applying strict allowlist validation for operation names and argument values
  • Avoiding unnecessary use of root privileges for restart and diagnostic utilities
  • Separating privileged helper processes from web-facing request handlers
  • Enforcing authorization checks at the operation boundary, not only at login
  • Limiting management-interface exposure and requiring secure administrative channels
  • Preserving audit logs for privileged command execution and rejected input

How teams detect issues like this

Organizations can look for command injection risks through:

  • Static analysis rules identifying shell invocation and string concatenation involving request parameters
  • Code review checks for web handlers that pass user-controlled values to system utilities
  • Verification that privileged helpers use fixed operations and validated arguments
  • Runtime monitoring for unexpected child processes, shell interpreters, or command executions originating from the web service
  • Policy enforcement requiring parameterized process APIs and least-privilege service accounts

Automated code-review and application-security tools may help identify suspicious command-construction patterns, but findings should be validated against the execution context.

Sources

SourceLink
en.mbs-solutions.deen.mbs-solutions.de/mbs
en.mbs-solutions.deen.mbs-solutions.de/xserie
github.comgithub.com/SilviaMun/vulnerability-research/tree/main/CVE-2026-75161

Frequently asked

questions

Yes. The attack surface is a remotely accessible web interface, but exploitation requires authentication and the appropriate Standard-role access.

No. The described condition involves a low-privileged authenticated Standard user. The security impact is significant because the invoked utility executes with root privileges.

Avoid constructing shell commands from request data. Use fixed operation mappings, strict allowlists, parameterized process execution, and a minimally privileged helper where system actions are necessary.

Apply secure coding checks to every system-command boundary, review privilege transitions, restrict management-interface access, and monitor web services for unexpected privileged child processes.

Find out what's already
exploitable in your codebase.