/

CVE-2026-75985

Severity:

HIGH RISK

(7.4)

Command Injection (CWE-77) in TRENDnet Router Firmware

CVE-2026-75985

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-74, CWE-77

Impact:

Remote Code Execution

Severity:

HIGH RISK

(7.4)

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 high-severity command injection flaw in TRENDnet Router 1.1.02b01 affects the /cgi-bin/ping.cgi interface. If a remotely supplied wan_type value reaches an unsafe command-construction path, an attacker may cause the router to execute operating-system commands.

Affected context

The vulnerability occurs in a router CGI endpoint that processes the wan_type argument. It is relevant where the affected web interface is reachable by an attacker and the argument is incorporated into an operating-system command without sufficient separation, validation, or safe API usage.

Exploit preconditions

  • Attack surface: The router's HTTP or HTTPS CGI interface
  • Required access: Network reachability to the affected /cgi-bin/ping.cgi endpoint; authentication requirements depend on the router's access controls
  • Trigger point: Processing of the wan_type argument
  • Why exploitation is possible: Attacker-controlled input may be interpreted as part of a system command rather than as a constrained data value

Why this happens

The underlying flaw is an unsafe boundary between web-request data and operating-system command execution. When an application builds or invokes a shell command using insufficiently constrained input, command syntax can be interpreted as executable instructions. This behavior maps primarily to CWE-77: Improper Neutralization of Special Elements used in a Command, with CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component describing the broader injection class.

Potential impact

  • An attacker may execute arbitrary commands with the privileges of the router's web service
  • The device could be modified, disrupted, or rendered unavailable
  • Network traffic, credentials, or configuration data could be exposed
  • The router could be used to access or attack other systems on connected networks

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from request-processing paths and reducing the trust placed in network input.

Common defensive patterns include:

  • Use dedicated system APIs with structured arguments instead of shell command construction
  • Apply allowlist validation for values such as interface or connection-type identifiers
  • Reject unexpected formats, lengths, encodings, and characters before processing
  • Run CGI and management components with the least privileges necessary
  • Restrict administrative interfaces to trusted management networks and require strong authentication
  • Apply network segmentation and minimize unnecessary exposure of router management services

How teams detect issues like this

Organizations can look for command injection risks through:

  • Static analysis rules identifying shell invocation or command concatenation with request parameters
  • Code review checks for CGI arguments passed into system, shell, or process-execution APIs
  • Tests that verify strict allowlist validation and structured argument handling
  • Web and device logs showing unusual requests to CGI endpoints or unexpected wan_type values
  • Policy enforcement that prevents administrative interfaces from being exposed beyond approved management networks

Automated security review tools may help identify unsafe data flows from HTTP parameters to command-execution functions.

Sources

SourceLink
github.comgithub.com/meishigana/CVE/blob/main/team15_20260702/12_823dru-ssi-cmdi/poc/poc-ssi-injection.py
github.comgithub.com/meishigana/CVE/tree/main/team15_20260702/12_823dru-ssi-cmdi
vuldb.comvuldb.com/cve/CVE-2026-75985
vuldb.comvuldb.com/submit/877809
vuldb.comvuldb.com/vuln/391904
vuldb.comvuldb.com/vuln/391904/cti

Frequently asked

questions

Yes, the described attack may be initiated remotely when the affected CGI endpoint is reachable and the request reaches the vulnerable processing path.

The available description does not establish a specific authentication requirement. Exposure and authentication depend on the router's management-interface configuration and network access controls.

Avoid constructing shell commands from request data. Prefer structured system APIs, strict allowlists, and least-privilege execution for management services.

Review all flows from web parameters to process execution, enforce input-validation policies, limit administrative exposure, and monitor CGI requests for anomalous values.

Find out what's already
exploitable in your codebase.