/

CVE-2026-82692

Severity:

CRITICAL RISK

(9.9)

OS Command Injection (CWE-78) in D-Link iSCSI Manager

CVE-2026-82692

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.9)

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 OS command injection vulnerability in the D-Link DNS-340L and DNS-345 iSCSI management CGI allows attacker-controlled parameter values to reach operating-system command execution. Because the affected endpoint may be reachable remotely, an unauthenticated or authenticated attacker, depending on deployment controls, could execute commands with the privileges of the web service.

Affected context

The vulnerability affects D-Link DNS-340L and DNS-345 devices in the affected release range when the /cgi-bin/iscsi_mgr.cgi endpoint processes user-controlled values for parameters such as alias, username, password, or volume_location. Risk is highest when the management interface is exposed to untrusted networks and the CGI process has broad system privileges.

Exploit preconditions

  • Attack surface: The HTTP-accessible iSCSI management CGI endpoint
  • Required access: Network reachability to the device; authentication requirements may depend on the device's administrative configuration
  • Trigger point: Processing of attacker-controlled iSCSI management parameters
  • Why exploitation is possible: Input is incorporated into an operating-system command path without sufficiently separating data from command syntax
  • Exploit availability: Public exploit information may increase scanning and attack activity

Why this happens

The underlying bug is command injection caused by passing externally supplied parameter values into an operating-system command or shell-processing path without robust argument separation and validation. This maps primarily to CWE-78: Improper Neutralization of Special Elements used in an OS Command, with CWE-77: Improper Neutralization of Special Elements in Command describing the broader command-construction weakness. The insecure pattern is treating request parameters as trusted command components rather than as constrained data.

Potential impact

  • An attacker may execute arbitrary commands on the affected device
  • The attacker could read, modify, or delete files accessible to the service
  • Device credentials, storage data, or configuration information could be exposed
  • The device could be used for persistence, lateral movement, or additional attacks
  • Availability could be reduced through service disruption or destructive commands

General mitigation guidance

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

Common defensive patterns include:

  • Using direct process-execution APIs with fixed executables and separately passed arguments rather than shell command strings
  • Applying allowlists and strict type, length, and character validation to iSCSI parameters
  • Rejecting unexpected values before any system interaction occurs
  • Restricting administrative interfaces to trusted management networks or protected access paths
  • Running CGI handlers with least privilege and isolating storage and system capabilities
  • Disabling unnecessary management services and applying network policy enforcement
  • Treating credentials and configuration values as data, never as command fragments

How teams detect issues like this

Detection can combine source review, runtime monitoring, and administrative policy controls.

Useful approaches include:

  • Static analysis rules for shell invocation, command concatenation, and process execution using request parameters
  • Code review checks for string interpolation involving CGI variables and system utilities
  • Web application monitoring for unusual requests to /cgi-bin/iscsi_mgr.cgi and unexpected parameter characters or lengths
  • Endpoint telemetry that flags CGI processes spawning shells or uncommon child processes
  • Network policies restricting access to device administration endpoints
  • Automated security review tools that identify command construction and missing input validation

Sources

SourceLink
github.comgithub.com/dxz0069/WAVLINK-WN530H4-Command-Injection-in-set_add_routing/blob/main/DLINK-CMD-006-vulndb.md
vuldb.comvuldb.com/cve/CVE-2026-82692
vuldb.comvuldb.com/submit/894211
vuldb.comvuldb.com/vuln/397180
vuldb.comvuldb.com/vuln/397180/cti
dlink.comdlink.com/

Frequently asked

questions

Yes. The affected CGI endpoint can be reached remotely when the device's management interface is network-accessible. The practical scope depends on network exposure and authentication controls.

The supplied description does not establish a universal authentication requirement. Access requirements may vary with device configuration, so management endpoints should not be exposed to untrusted networks.

Avoid shell-based command construction, pass arguments through APIs that preserve argument boundaries, and enforce strict allowlist validation before processing input.

Apply secure coding rules for process execution, use least-privilege service accounts, restrict management-plane access, and monitor for abnormal CGI activity and child-process creation.

Find out what's already
exploitable in your codebase.