/

CVE-2026-75984

Severity:

HIGH RISK

(7.4)

Command Injection (CWE-77) in TRENDnet TEW-823DRU Router

CVE-2026-75984

Deferred

Vulnerability type

Category:

Command Injection

CWE:

CWE-74, CWE-77

Impact:

Remote Operating-System Command 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 command injection vulnerability in the TRENDnet TEW-823DRU router affects handling of the Hostname argument in an administrative CGI endpoint. A remote attacker may be able to execute operating-system commands when the endpoint is reachable and accepts attacker-controlled input without adequate separation from command syntax.

Affected context

The vulnerability occurs in the router's web administration interface, specifically the /cgi-bin/admin.cgi endpoint and its handling of the Hostname argument. Risk is higher when the administration interface is reachable from an untrusted network and the supplied value is processed by a shell or command-execution routine without robust validation and argument separation.

Exploit preconditions

  • Attack surface: Network-accessible router administration CGI endpoint
  • Required access: Ability to reach the affected administrative interface; authentication requirements depend on the device's access controls
  • Trigger point: Processing of the Hostname argument by the administrative function
  • Why exploitation is possible: Attacker-controlled input may be interpreted as part of an operating-system command rather than as data

Why this happens

The underlying bug is an injection flaw in which externally supplied data is incorporated into an operating-system command without a sufficiently separated execution interface or strict validation. This behavior maps primarily to CWE-77: Command Injection and is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component, because input intended as a hostname may be interpreted as command syntax by a downstream shell or command processor.

Potential impact

  • An attacker may execute commands with the privileges of the affected router service.
  • The device could be modified, disrupted, or made unavailable.
  • Network traffic or configuration data could be exposed or altered.
  • The router could be used to access or attack other systems on connected networks.
  • Persistent compromise or use of the device in broader malicious activity could occur.

General mitigation guidance

Mitigation generally focuses on preventing untrusted values from reaching shell interpretation and reducing the privileges of affected services.

Common defensive patterns include:

  • Passing arguments through APIs that do not invoke a shell.
  • Applying strict allowlist validation for hostname-like values and rejecting unexpected characters or structures.
  • Treating administrative input as untrusted even when it comes from an authenticated user.
  • Restricting management interfaces to trusted networks and avoiding unnecessary Internet exposure.
  • Running command-processing services with the minimum practical privileges.
  • Separating configuration updates from command execution and enforcing secure-by-default management access controls.

How teams detect issues like this

Organizations commonly detect command injection risks through:

  • Static analysis rules for shell invocation, command construction, and string concatenation involving request parameters.
  • Code review checks for CGI parameters passed to shell wrappers or process-spawning functions.
  • Runtime monitoring for unexpected child processes, unusual command execution, or administrative requests containing shell metacharacters.
  • Network policy enforcement that limits access to device management endpoints.
  • Automated security review tools that identify tainted input flows into command-execution sinks.

Sources

SourceLink
github.comgithub.com/meishigana/CVE/blob/main/team15_20260702/11_823dru-rc-cmdi/poc/poc-rc-injection.py
github.comgithub.com/meishigana/CVE/tree/main/team15_20260702/11_823dru-rc-cmdi
vuldb.comvuldb.com/cve/CVE-2026-75984
vuldb.comvuldb.com/submit/877798
vuldb.comvuldb.com/vuln/391903
vuldb.comvuldb.com/vuln/391903/cti

Frequently asked

questions

The reported issue can be reached remotely through the affected CGI endpoint when the router's administration interface is network-accessible. Actual exploitability depends on exposure, authentication, and deployment controls.

The available description does not establish whether authentication is required. Access to the administrative endpoint and any configured authorization barriers are key factors.

Avoid shell interpretation for user-controlled values, use direct process APIs with separated arguments, and enforce strict allowlist validation for hostname fields.

Keep management interfaces limited to trusted networks, apply least privilege, review all input-to-command data flows, and use static analysis and runtime monitoring to detect unsafe command construction.

Find out what's already
exploitable in your codebase.