Skip to main content
VulnerabilityPublished

CVE-2026-4205: D-Link DNS-120 · Command Injection

Affects D-Link DNS-120Source CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.9% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
D-LinkDNS-120Affected
  • =20260205
Fixed in–
D-LinkDNR-202LAffected
  • =20260205
Fixed in–
D-LinkDNS-315LAffected
  • =20260205
Fixed in–
D-LinkDNS-320Affected
  • =20260205
Fixed in–
D-LinkDNS-320LAffected
  • =20260205
Fixed in–
D-LinkDNS-320LWAffected
  • =20260205
Fixed in–

AI-suggested

To mitigate CVE-2026-4205, organizations should first verify if their D-Link NAS devices are among the affected models and running vulnerable firmware versions up to 20260205. Immediate steps include: 1) Applying any available firmware updates or patches from D-Link as soon as they are released. 2) If patches are not yet available, restrict network access to the management interface by implementing firewall rules to limit access to trusted IP addresses only. 3) Disable remote management features if not required, especially access to the CGI scripts involved. 4) Employ network segmentation to isolate NAS devices from critical internal networks and the internet. 5) Monitor network traffic and device logs for unusual activity indicative of exploitation attempts targeting the CGI endpoints. 6) Consider deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with signatures to detect and block command injection attempts. 7) Educate administrators on the risk and ensure strong credentials and multi-factor authentication are used where possible to reduce attack surface. 8) Regularly back up NAS data to separate, secure storage to mitigate data loss risks. These targeted mitigations go beyond generic advice by focusing on access control, monitoring, and network architecture adjustments specific to the vulnerability's attack vector.

Description

A vulnerability has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05 and DNS-1550-04 up to 20260205. The impacted element is the function cgi_refresh_db/FTP_Server_BlockIP_Add/FTP_Server_BlockIP_Del of the file /cgi-bin/app_mgr.cgi. Such manipulation leads to command injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…