/

CVE-2026-90702

Severity:

CRITICAL RISK

(9.1)

OS Command Injection (CWE-78) in D-Link DWR-M921 Router

CVE-2026-90702

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.1)

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 flaw in the D-Link DWR-M921 affects the partition argument processed by the /boafrm/formDiskFormat function. An attacker who can reach the exposed management function may be able to execute operating-system commands on the router, depending on access controls and deployment configuration.

Affected context

The vulnerability occurs in D-Link DWR-M921 firmware version 1.1.52 when the router processes partition-related input through the /boafrm/formDiskFormat endpoint. Risk is greatest when the device's web management interface is reachable by an attacker and the endpoint accepts insufficiently constrained input.

Exploit preconditions

  • Attack surface: The router's web management interface and the /boafrm/formDiskFormat function
  • Required access: Network reachability and any authentication or authorization required by the exposed management interface
  • Trigger point: Processing of the partition argument during the disk-format operation
  • Why exploitation is possible: User-controlled input may be incorporated into an operating-system command without adequate separation, validation, or escaping

Why this happens

The underlying bug is command construction that treats externally influenced input as part of an operating-system command. If shell metacharacters or command syntax are not safely rejected or isolated, the input can alter command interpretation rather than remain a data value. 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-injection class.

Potential impact

  • An attacker may execute arbitrary commands with the privileges of the affected service
  • The router could be compromised or rendered unavailable
  • Network traffic may be monitored, redirected, or disrupted
  • Device configuration and stored data could be altered
  • A compromised router could be used for lateral movement or further attacks

General mitigation guidance

Mitigation generally focuses on preventing user-controlled values from reaching shell command interpreters.

Common defensive patterns include:

  • Replacing shell command construction with structured APIs that pass arguments separately
  • Enforcing strict allowlists for partition identifiers and rejecting unexpected input
  • Applying contextual validation before invoking storage-management operations
  • Running management services and helper processes with the least privileges necessary
  • Restricting management interfaces to trusted networks and disabling unnecessary remote exposure
  • Using layered authorization and audit logging for sensitive formatting operations

These controls reduce command-injection risk and limit the consequences if an input-validation boundary fails.

How teams detect issues like this

Organizations can assess for this weakness through:

  • Static analysis rules that identify shell execution APIs receiving request parameters
  • Code review checks for string concatenation or interpolation in command construction
  • Tests using benign metacharacter and delimiter handling cases to verify strict rejection
  • Network policies that detect or prevent exposure of administrative endpoints to untrusted networks
  • Runtime monitoring for unexpected process creation, command execution, or configuration changes by the web service

Automated security review tools may help identify command-sink data flows, but findings should be validated against the device's actual request and authorization paths.

Sources

SourceLink
gist.github.comgist.github.com/H3rmesk1t/1f7efbf4584ce13222e8b0c669e7784a
vuldb.comvuldb.com/cve/CVE-2026-90702
vuldb.comvuldb.com/submit/917692
vuldb.comvuldb.com/vuln/403244
vuldb.comvuldb.com/vuln/403244/cti
dlink.comdlink.com/

Frequently asked

questions

It may be remotely exploitable when the router's management interface and affected function are reachable by an attacker. Practical exploitability depends on network exposure, authentication, authorization, and other deployment controls.

The attacker generally needs network access to the relevant management endpoint and must satisfy any access controls enforced by the device. Exposure to untrusted networks substantially increases risk.

The safest pattern is to avoid shell interpretation entirely, pass validated values through structured operating-system APIs, and enforce a strict allowlist for permitted partition values.

Minimize management-interface exposure, apply least privilege, review all command-execution paths, validate inputs at trust boundaries, and monitor administrative services for unexpected child processes.

Find out what's already
exploitable in your codebase.