D-Link DNS 320 Vulnerabilities
52 known CVEs, 3 critical, 4 in CISA's Known Exploited Vulnerabilities catalog. Last updated 2026-10-24.
Known CVEs
The login_mgr.cgi script in D-Link DNS-320 through 2.05.B10 is vulnerable to remote command injection.
D-Link DNS-320 FW v2.06B01 Revision Ax is affected by command injection in the system_mgr.cgi component, which can lead to remote arbitrary code execution.
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as very critical, has been found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to 20240403. This issue affects some unknown processing of t...
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified as critical was 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, DN...
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, 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-...
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, was 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,...
** UNSUPPORTED WHEN ASSIGNED ** 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, D...
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was 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-34...
A weakness has been identified 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, D...
A security vulnerability has been detected 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, D...
Commonly exposed ports
- Port 23 (Telnet) — Sends admin credentials unencrypted — a common target on older router firmware.
- Port 80 (HTTP admin panel) — The web admin UI; dangerous if remote/WAN administration is left enabled.
- Port 7547 (TR-069 (CWMP)) — ISP remote-management protocol — has been the entry point for several router botnets.
- Port 1900 (UPnP/SSDP) — Lets apps on your LAN open firewall holes automatically, sometimes without your knowledge.
Default credentials
From ProbeShield's own tested default-credential list (see probeshield.com/default-passwords/): "admin" / "d-link" or "admin" / "pass" over HTTP.
Hardening checklist
- Disable remote (WAN-side) administration unless you specifically need it.
- Turn off UPnP unless a specific app you trust requires it.
- Turn off WPS — it can let an attacker bypass your Wi-Fi password.
- Change the default admin username and password to something unique.
- Check for a firmware update in the router’s admin panel and apply it.
- Disable Telnet/SSH management access if you don’t actively use it.
Frequently asked questions
Is my D-Link DNS 320 affected by these vulnerabilities? Only if you’re running a firmware version in the affected range listed above and haven’t updated. Check your router's admin panel for its current firmware version and compare it against the ranges below.
How do I update my D-Link DNS 320's firmware? Log into the router's web admin panel (usually at its local IP address) and look for a Firmware Update or System Update section, or use the vendor's mobile app if it has one.
Does ProbeShield fix these vulnerabilities for me? No — ProbeShield scans your network and tells you what it finds (open ports, default credentials, outdated firmware signals) so you know what to fix, and how. It never changes your devices’ settings.
Sources: National Vulnerability Database (NVD), CISA Known Exploited Vulnerabilities Catalog. This page lists which firmware versions are affected — it doesn't claim your specific unit is vulnerable. Check your device's current firmware version in its admin panel and compare it against the ranges above.