/

CVE-2026-76583

Severity:

HIGH RISK

(7.4)

Command Injection (CWE-74) in TRENDnet TV-IP751WIC CGI

CVE-2026-76583

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 TV-IP751WIC's alphapd web component allows attacker-controlled input to influence operating-system command execution through the set_time.cgi functionality. Because the attack can be initiated remotely, an exposed and reachable device may be at risk without local access.

Affected context

The vulnerability occurs in the alphapd component's /cgi-bin/admin/set_time.cgi endpoint on affected TRENDnet TV-IP751WIC devices. Risk depends on whether the device exposes the management interface to an attacker and whether request data reaches command-processing logic without adequate separation, validation, or escaping.

Exploit preconditions

  • Attack surface: Network-accessible device management web interface
  • Required access: Ability to send requests to the affected CGI endpoint; authentication requirements may depend on the device's configuration
  • Trigger point: Processing of attacker-influenced input by set_time.cgi
  • Why exploitation is possible: Input is incorporated into an operating-system command context without sufficient command and argument separation

Why this happens

The underlying bug is an operating-system command injection condition. A web-facing CGI handler appears to pass externally influenced data into command execution logic without treating the data strictly as a value.

This maps primarily to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') and is also associated with CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'). The insecure pattern occurs when application input crosses into a shell or command interpreter without a safe argument-oriented interface and strict validation.

Potential impact

  • An attacker may execute commands with the privileges of the device service
  • The device could be disrupted, reconfigured, or rendered unavailable
  • Configuration data or connected network information could be exposed
  • The compromised device could be used to access or attack adjacent systems
  • Malware or persistence mechanisms could be installed where device permissions allow

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from request-processing paths and reducing trust in network-provided values.

Common defensive patterns include:

  • Prefer direct, argument-based operating-system APIs over shell command construction
  • Apply strict allowlist validation for time, date, and related configuration fields
  • Use typed parsing and canonicalization before values reach privileged operations
  • Ensure management interfaces are isolated from untrusted networks and protected by strong access controls
  • Run device services with the minimum privileges needed for normal operation
  • Apply secure-by-default network segmentation and disable unnecessary remote administration exposure
  • Treat client-side validation as insufficient and enforce controls on the device

How teams detect issues like this

Detection approaches may include:

  • Static analysis for string concatenation or formatting of request data into shell commands
  • Code review checks for shell invocation from CGI handlers and administrative endpoints
  • Runtime monitoring for unusual child-process creation by the alphapd service
  • Web-server and device logs showing anomalous requests to set_time.cgi
  • Network policies that alert on unexpected outbound connections from the device
  • Automated security review tools that identify command execution APIs receiving unsanitized input

Sources

SourceLink
github.comgithub.com/meishigana/CVE/blob/main/team15_20260702/07_751wic-apd-time-cmdi/poc/poc-time-injection.py
github.comgithub.com/meishigana/CVE/tree/main/team15_20260702/07_751wic-apd-time-cmdi
vuldb.comvuldb.com/cve/CVE-2026-76583
vuldb.comvuldb.com/submit/877792
vuldb.comvuldb.com/vuln/393042
vuldb.comvuldb.com/vuln/393042/cti

Frequently asked

questions

Yes. The reported attack surface is a remotely reachable CGI endpoint, although practical exploitability depends on network exposure, authentication, and device configuration.

No local access is inherently required. An attacker generally needs network reachability to the management interface and whatever access the endpoint requires.

Avoid passing request data through a shell or command interpreter. Use fixed operations with typed, allowlisted arguments and enforce validation on the device.

Combine secure command-execution APIs, strict input validation, least-privilege service accounts, restricted management exposure, and static analysis focused on injection-sensitive code paths.

Find out what's already
exploitable in your codebase.