Home › Intelligence › Brief
VULNERABILITY BRIEF🔴 Critical Vulnerability

Critical OS Command Injection (CVE‑2024‑10914) Affects Multiple D‑Link NAS Models, No Patch Planned

A remote, unauthenticated command injection (CVE‑2024‑10914) in D‑Link NAS devices allows attackers to run arbitrary root commands. The devices are End‑of‑Life and will not be patched, creating a high‑severity exposure for any organization still using them. This underscores the need for continuous vendor‑risk monitoring and SOC 2‑aligned evidence of mitigation.

LiveThreat™ Intelligence · 📅 August 18, 2026· 📰 exploit-db.com
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
exploit-db.com

Critical OS Command Injection (CVE‑2024‑10914) Affects Multiple D‑Link NAS Models, No Patch Planned

What Happened – A remote, unauthenticated OS command injection flaw (CVE‑2024‑10914) was discovered in the /cgi-bin/account_mgr.cgi script of several D‑Link NAS appliances (DNS‑320, DNS‑320LW, DNS‑325, DNS‑340L). The vulnerable cgi_user_add endpoint concatenates the name parameter into a system() call, allowing an attacker to execute arbitrary commands with root privileges. D‑Link has declared the affected models End‑of‑Life and will not release a fix, and evidence of active exploitation in the wild exists.

Why It Matters for Compliance & Audit Readiness

  • The flaw illustrates why continuous third‑party device risk monitoring is a core SOC 2 control (CC6.1 – System and Communications Protection).
  • Without documented evidence that you assess and mitigate vendor‑supplied hardware risks, auditors will question the effectiveness of your risk‑management program.

Who Is Affected – Organizations that deploy D‑Link NAS devices across any industry (e.g., SMBs, education, healthcare, retail).

Recommended Actions

  • Inventory all D‑Link NAS units and verify firmware versions against the vulnerable list.
  • Segregate vulnerable devices from critical networks; apply network‑level filtering to block the /cgi-bin/account_mgr.cgi endpoint.
  • Initiate a vendor‑risk review: document the exposure, assess business impact, and record mitigation steps as audit evidence.
  • Consider replacing EOL hardware with a supported solution that provides regular security updates.

Technical Notes – The vulnerability is a classic unauthenticated command injection (CVSS 3.1 9.8 Critical). Exploitation requires only a crafted HTTP GET request to the vulnerable CGI script. No authentication or prior access is needed. Source: Exploit‑DB 52643

📰 Original Source
https://www.exploit-db.com/exploits/52643 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Vendor Risk Hub

This is the scenario continuous vendor monitoring is built to catch.

When a vendor is compromised, your third-party risk controls are what produce the audit trail showing you knew, assessed, and acted. The Verisq AI Trust Operations platform tracks that continuously.

Explore the Verisq AI Trust Operations platform →