/

CVE-2026-19379

Severity:

HIGH RISK

(7.3)

OS Command Injection (CWE-78) in ipTIME AX8004M CGI

CVE-2026-19379

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Code Execution

Severity:

HIGH RISK

(7.3)

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 remotely reachable CGI endpoint in the EFM ipTIME AX8004M may pass attacker-controlled fname input to an operating-system command through popen.

An attacker who can reach the endpoint and supply crafted input could execute commands with the privileges of the web service, making this a high-severity risk.

Affected context

The vulnerability occurs in the /cgi/d.cgi CGI endpoint of affected ipTIME AX8004M firmware when the fname argument reaches command-execution logic without adequate separation from shell syntax. Risk depends on network exposure of the management or CGI interface, request handling, and the privileges available to the underlying service.

Exploit preconditions

  • Attack surface: The remotely accessible /cgi/d.cgi CGI endpoint
  • Required access: Network reachability to the affected endpoint; authentication requirements may depend on device configuration
  • Trigger point: Processing of the fname argument by the endpoint's popen call
  • Why exploitation is possible: Attacker-controlled input is incorporated into an operating-system command without sufficient command and argument boundary enforcement

Why this happens

The underlying bug is OS command injection, mapped primarily to CWE-78: Improper Neutralization of Special Elements used in an OS Command. The endpoint treats externally supplied data as part of a command executed through popen, allowing command syntax to alter the intended operation. This is also related to CWE-77: Improper Neutralization of Special Elements in Command, which covers broader command construction failures.

Potential impact

  • An attacker may execute arbitrary commands with the web service's privileges.
  • The device could be compromised or used as a foothold for further network activity.
  • Configuration, credentials, or other device data could be exposed or modified.
  • Network traffic could be disrupted, redirected, or monitored.
  • The device could be incorporated into broader malicious activity.

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from request processing and reducing trust in endpoint parameters.

Common defensive patterns include:

  • Replacing shell-based command execution with direct, fixed-function APIs that pass arguments separately.
  • Applying strict allowlists for permitted fname values and rejecting unexpected characters, paths, and encodings.
  • Performing canonicalization and validation before any system operation, while avoiding validation as the sole defense.
  • Restricting administrative and CGI endpoint exposure through network segmentation and access controls.
  • Running web-facing services with the minimum operating-system privileges and filesystem access required.
  • Using secure-by-default management interfaces and disabling unnecessary remote administration paths.

How teams detect issues like this

Detection can include static analysis for popen, shell invocation, command concatenation, and externally controlled arguments reaching process-launch APIs. Code reviews should examine CGI parameters, path or filename handling, quoting assumptions, and whether direct execution APIs are used instead of shell interpretation. Runtime monitoring may alert on unusual requests to /cgi/d.cgi, unexpected command-related child processes, abnormal process trees, or management-interface access from untrusted networks. CI policy checks can flag shell execution that receives data from HTTP parameters.

Sources

SourceLink
github.comgithub.com/seting-and-break/vulnerability-reports/blob/main/ipTIME_AX8004M_Vulnerability_Report.md
vuldb.comvuldb.com/cve/CVE-2026-19379
vuldb.comvuldb.com/submit/866635
vuldb.comvuldb.com/vuln/387272
vuldb.comvuldb.com/vuln/387272/cti

Frequently asked

questions

Yes. The affected CGI endpoint can be reached remotely when the device interface is network-accessible, although authentication and network controls may affect practical exploitability.

The attacker needs network reachability to the CGI endpoint and sufficient ability to submit or influence the fname argument. Whether authentication is required depends on the device's deployment and access configuration.

Avoid passing request-derived data to a shell. Use fixed-function or direct process APIs, enforce strict allowlists, and run the service with least privilege.

Treat all CGI parameters as untrusted, apply structured validation, limit administrative interface exposure, and use static analysis and code-review policies that identify shell command construction.

Find out what's already
exploitable in your codebase.