Security Resilience

CVE-2024-23625

Command Injection in Dlink Dap-1650 Firmware

Published
26 January 2024
Modified
17 June 2026
CVSS Score v3.1 9.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.073 94th percentile
Risk Priority 81 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-23625 is a critical-severity Command Injection (CWE-77) vulnerability in Dlink Dap-1650 Firmware. Its CVSS base score is 9.6 (Critical).

Operationally, ranked in the top 6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A command injection vulnerability exists in D-Link DAP-1650 devices when handling UPnP SUBSCRIBE messages. The flaw, tracked as CVE-2024-23625 and assigned CWE-77, allows unauthenticated remote attackers to inject and execute arbitrary commands. It carries a CVSS 3.1 score of 9.6 with an attack vector of adjacent network, low complexity, and no required privileges or user interaction, resulting in complete confidentiality, integrity, and availability impact with scope change.

An attacker positioned on the same network segment as an affected DAP-1650 device can send a crafted UPnP SUBSCRIBE message that triggers the injection. Successful exploitation grants command execution on the device with root privileges, enabling full control over the router's configuration, traffic, and connected clients.

The EPSS score for this CVE has remained flat at 0.1001 since disclosure, indicating no material increase in observed exploitation interest.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A command injection vulnerability exists in D-Link DAP-1650 devices when handling UPnP SUBSCRIBE messages. An unauthenticated attacker can exploit this vulnerability to gain command execution on the device as root.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-23624Same product: Dlink Dap-1650
CVE-2024-40505Same product: Dlink Dap-1650
CVE-2025-46176Same vendor: Dlink
CVE-2024-22651Same vendor: Dlink
CVE-2024-44400Same vendor: Dlink
CVE-2023-26822Same vendor: Dlink
CVE-2023-39637Same vendor: Dlink
CVE-2025-60698Same vendor: Dlink
CVE-2025-60701Same vendor: Dlink
CVE-2023-33625Same vendor: Dlink

Affected Assets

dlink
dap-1650 firmware
all versions

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References