DSL-2640B: Missing Authentication for Critical Functionality
CVE-2026-0625 is a critical-severity missing authentication for critical functionality vulnerability in DSL-2640B from D-Link, with a CVSS 4.0 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected DSL-2640B versions: 0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.97% chance of exploitation within 30 days, higher than 63% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of DSL-2640B you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| D-Link | DSL-2640B | 0 | Not stated |
| D-Link | DSL-2740R | 0 | Not stated |
| D-Link | DSL-2780B | 0 | Not stated |
| D-Link | DSL-526B | 0 | Not stated |
| D-Link | DSL-2640T | 0 | Not stated |
| D-Link | DSL-500 | 0 | Not stated |
| D-Link | DSL-500G | 0 | Not stated |
| D-Link | DSL-502G | 0 | Not stated |
| D-Link | DIR-905L | 0 | Not stated |
| D-Link | DIR-600 | 0 | Not stated |
| D-Link | DIR-608 | 0 | Not stated |
| D-Link | DIR-610 | 0 | Not stated |
| D-Link | DIR-611 | 0 | Not stated |
| D-Link | DIR-615 | 0 | Not stated |
| D-Link | DNS-320 | 0 | Not stated |
| D-Link | DNS-325 | 0 | Not stated |
| D-Link | DNS-345 | 0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- NoneNo loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- NoneNo loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- NoneNo loss of availability on systems beyond the vulnerable one.
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA (vulncheck.com).
Official description
Multiple D-Link DSL/DIR/DNS devices contain an authentication bypass and improper access control vulnerability in the dnscfg.cgi endpoint that allows an unauthenticated attacker to access DNS configuration functionality. By directly requesting this endpoint, an attacker can modify the device’s DNS settings without valid credentials, enabling DNS hijacking (“DNSChanger”) attacks that redirect user traffic to attacker-controlled infrastructure. In 2019, D-Link reported that this behavior was leveraged by the "GhostDNS" malware ecosystem targeting consumer and carrier routers. All impacted products were subsequently designated end-of-life/end-of-service, and no longer receive security updates. Exploitation evidence was observed by the Shadowserver Foundation on 2025-11-27 (UTC).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
- supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10068
- supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10118
- supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10488
- vulncheck.com/advisories/dlink-dsl-command-injection-via-dns-configuration-endpoint
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 8.2 High severity
- 9.8 Critical severity
- 9.1 Critical severity
- 7.5 High severity
Spotted an error? Tell us.