Severity:

CRITICAL RISK

(9.8)

Command Injection (CWE-78) in Totolink A7100RU Router

CVE-2026-5995

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Arbitrary Command Execution

Severity:

CRITICAL RISK

(9.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 critical command-injection weakness may exist in the setMiniuiHomeInfoShow function of Totolink A7100RU firmware. If attacker-controlled input reaches the affected CGI handler without adequate filtering, an attacker could cause the device to execute unintended operating-system commands.

Affected context

The issue is associated with the setMiniuiHomeInfoShow function in /cgi-bin/cstecgi.cgi on Totolink A7100RU devices running the affected firmware. Risk depends on whether the CGI endpoint is reachable, whether attacker-controlled data is accepted, and whether that data is incorporated into an operating-system command without effective separation or validation.

Exploit preconditions

  • Attack surface: The device's web management CGI interface
  • Required access: Access sufficient to reach the affected CGI request; authentication requirements depend on the device's deployment and endpoint controls
  • Trigger point: Processing of input by setMiniuiHomeInfoShow
  • Why exploitation is possible: Input may be incorporated into a shell or operating-system command without reliable command-boundary enforcement

Why this happens

The underlying bug is an OS command-injection pattern in which data supplied through a web-facing handler is used in command execution as though it were trusted. This behavior maps primarily to CWE-78, Improper Neutralization of Special Elements used in an OS Command, and is also related to CWE-77, which covers improper construction of commands from externally influenced data.

Potential impact

  • An attacker may execute commands with the privileges of the device service
  • Device configuration, credentials, or network information could be exposed
  • Network traffic could be redirected, disrupted, or manipulated
  • The device could be used to attack other systems on the local network
  • Persistence, denial of service, or broader compromise could occur

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from request

processing and reducing trust in externally supplied values.

Common defensive patterns include:

  • Prefer direct library or system APIs over shell command construction
  • Use fixed command and argument mappings rather than concatenating input
  • Apply allowlists and strict type and format validation at trust boundaries
  • Separate arguments using safe process-execution interfaces when execution is unavoidable
  • Run management services with the minimum privileges and filesystem access required
  • Restrict administrative interfaces to trusted management networks
  • Use secure-by-default configuration that disables unnecessary remote administration

How teams detect issues like this

Detection approaches may include:

  • Static analysis for shell invocation, command concatenation, and externally influenced arguments
  • Code review checks for CGI parameters flowing into process or system-execution APIs
  • Testing with metacharacter handling and boundary-separation cases in controlled environments
  • Web-application firewall or gateway policies limiting access to management CGI endpoints
  • Runtime monitoring for unexpected child processes, shell launches, or outbound connections from router services
  • Automated security review tools that identify CWE-77 and CWE-78 data-flow patterns

Sources

SourceLink
github.comgithub.com/Litengzheng/vuldb_new/blob/main/A7100RU/vul_167/README.md
vuldb.comvuldb.com/submit/792043
vuldb.comvuldb.com/vuln/356549
vuldb.comvuldb.com/vuln/356549/cti
totolink.nettotolink.net/

Frequently asked

questions

It may be remotely exploitable when the affected CGI endpoint is reachable over a

network and the request can reach the vulnerable code path. The exact scope

depends on management-interface exposure and access controls.

Not necessarily. Authentication requirements depend on how the device protects

the affected handler and how its management interface is configured.

Avoid constructing shell commands from request data. Use dedicated APIs, fixed

command mappings, strict allowlists, and least-privilege execution instead.

Treat all management-interface input as untrusted, review data flows into process

execution, restrict administrative exposure, and monitor for unexpected commands

or child processes.

Find out what's already
exploitable in your codebase.