D-Link DIR 615 Vulnerabilities
26 known CVEs, 9 critical, 1 in CISA's Known Exploited Vulnerabilities catalog. Last updated 2026-10-24.
Known CVEs
D-Link DIR-615 Wireless N 300 Router allows authentication bypass via a modified POST request to login.cgi. This issue occurs because it fails to validate the password field. Successful exploitation of this issue allo...
On the D-Link DIR-615 before v20.12PTb04, once authenticated, this device identifies the user based on the IP address of his machine. By spoofing the IP address belonging to the victim's host, an attacker might be abl...
The D-Link DIR-615 device before v20.12PTb04 doesn't use SSL for any of the authenticated pages. Also, it doesn't allow the user to generate his own SSL Certificate. An attacker can simply monitor network traffic to s...
D-Link DIR-615 before v20.12PTb04 has a second admin account with a 0x1 BACKDOOR value, which might allow remote attackers to obtain access via a TELNET connection.
D-Link DIR-615 devices have a buffer overflow via a long Authorization HTTP header.
Unauthenticated remote code execution occurs in D-Link products such as DIR-655C, DIR-866L, DIR-652, and DHP-1565. The issue occurs when the attacker sends an arbitrary input to a "PingTest" device common gateway inte...
A buffer overflow in D-Link DIR-615 C2 3.03WW. The ping_ipaddr parameter in ping_response.cgi POST request allows an attacker to crash the webserver and might even gain remote code execution.
The WAN configuration page "wan.htm" on D-Link DIR-615 devices with firmware 20.06 can be accessed directly without authentication which can lead to disclose the information about WAN settings and also leverage attack...
Multiple D-Link DIR-series routers, including DIR-110, DIR-412, DIR-600, DIR-610, DIR-615, DIR-645, and DIR-815 firmware version 1.03, contain a vulnerability in the service.cgi endpoint that allows remote attackers t...
D-Link DIR-615 HW: T1 FW:20.09 is vulnerable to Cross-Site Request Forgery (CSRF) vulnerability. This enables an attacker to perform an unwanted action on a wireless router for which the user/admin is currently authen...
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 DIR 615 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 DIR 615'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.