/

CVE-2026-90880

Severity:

HIGH RISK

(7.4)

OS Command Injection (CWE-77) in D-Link DSL-3782 Router

CVE-2026-90880

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 command injection vulnerability in the D-Link DSL-3782 diagnostics interface allows attacker-controlled input in the Addr argument to reach an operating system command execution path. Because the affected function may be reachable remotely, an attacker who can access the interface could potentially execute commands with the privileges of the router service.

Affected context

The issue occurs in the Diagnostics component of D-Link DSL-3782 firmware dated 2016-07-28, specifically in the /cgi-bin/New_GUI/Set/Diagnostics.asp endpoint. Risk is present when the endpoint is reachable by an attacker and the Addr parameter is incorporated into a system command without sufficient separation, validation, or escaping.

Exploit preconditions

  • Attack surface: The router's remotely reachable web management or diagnostics interface
  • Required access: Network access to the affected endpoint; authentication requirements may depend on device configuration
  • Trigger point: Processing of the Addr argument by the Diagnostics function
  • Why exploitation is possible: User-controlled input can reach an operating system command context without adequate command and argument separation

Why this happens

The underlying defect is an injection flaw in which externally supplied data is combined with an operating system command. If input is passed to a shell or command interpreter without strict validation and safe argument handling, command syntax may be interpreted as executable instructions rather than ordinary data. This maps primarily to CWE-77: Command Injection, with CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component describing the broader injection pattern.

Potential impact

  • An attacker may execute operating system commands on the router
  • Device configuration and credentials could be exposed or altered
  • Network traffic could be monitored, redirected, or disrupted
  • The router could be used for persistence, lateral movement, or attacks against other systems
  • Availability of the device and connected services could be reduced

General mitigation guidance

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

Common defensive patterns include:

  • Replacing shell command construction with direct library or system APIs
  • Passing fixed command arguments through structured process-execution interfaces
  • Applying strict allowlist validation to diagnostic address fields
  • Separating data from commands and avoiding shell evaluation
  • Restricting management interfaces to trusted administration networks
  • Running diagnostic services with the least privileges needed
  • Disabling or isolating unused remote management functionality

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules that identify request parameters concatenated into shell commands
  • Code review checks for calls to shell interpreters, command execution APIs, or string-built diagnostic commands
  • Tests that verify address and host fields are treated as structured data rather than command text
  • Web and router logs showing unusual requests to the Diagnostics endpoint or malformed Addr values
  • Network monitoring for unexpected outbound connections or configuration changes from the router
  • Policy enforcement requiring allowlist validation and non-shell process execution for management interfaces

Automated security review tools may help identify command-construction patterns, but findings should be validated against the actual execution path.

Sources

SourceLink
github.comgithub.com/MeetFireAgain/cve/tree/main/dlink-dsl3782
vuldb.comvuldb.com/cve/CVE-2026-90880
vuldb.comvuldb.com/submit/928835
vuldb.comvuldb.com/vuln/403474
vuldb.comvuldb.com/vuln/403474/cti
dlink.comdlink.com/

Frequently asked

questions

Potentially. The affected diagnostics endpoint may be reachable over the network, but practical exploitability depends on interface exposure, authentication, and device configuration.

An attacker needs network access to the affected endpoint. Whether authentication is required depends on how the router's management interface is configured.

Avoid constructing shell commands from request data. Use direct APIs with fixed operations, structured arguments, and strict allowlist validation for diagnostic parameters.

Keep management interfaces isolated, minimize service privileges, apply secure input-handling policies, and use code review or automated analysis to detect shell command construction from external input.

Find out what's already
exploitable in your codebase.