CVE-2026-1705VulnerabilityPublished 30 Jan 2026Updated 23 Feb 2026

CVE-2026-1705: D-Link DSL-6641K · Cross Site Scripting

Affects D-Link DSL-6641KSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
D-LinkDSL-6641K	Affected =N8.TR069.20131126	Fixed in–

AI-suggested

1. Monitor D-Link’s official channels for firmware updates or patches addressing CVE-2026-1705 and apply them promptly once available. 2. Until patches are released, restrict access to the router’s web interface by limiting management access to trusted IP addresses or internal networks only, using firewall rules or VPNs. 3. Disable remote management features if not required to reduce exposure to remote exploitation. 4. Educate users about the risks of clicking on suspicious links or visiting untrusted websites that could trigger the XSS attack. 5. Employ web application firewalls (WAFs) or intrusion prevention systems (IPS) capable of detecting and blocking malicious payloads targeting the router’s web interface. 6. Regularly audit router configurations and logs for unusual activity indicative of exploitation attempts. 7. Consider network segmentation to isolate vulnerable devices from critical infrastructure and sensitive data. 8. Implement strong authentication and session management controls on network devices to limit the impact of session hijacking. 9. Use browser security features such as Content Security Policy (CSP) where possible to mitigate XSS risks on client endpoints. 10. Plan for device replacement if vendor support or patch availability is insufficient to address the vulnerability.

Description

A vulnerability was detected in D-Link DSL-6641K N8.TR069.20131126. Affected by this issue is the function ad_virtual_server_vdsl of the component Web Interface. Performing a manipulation of the argument Name results in cross site scripting. It is possible to initiate the attack remotely. The exploit is now public and may be used.

Impact

The primary impact of CVE-2026-1705 is the potential for attackers to execute arbitrary scripts in the context of the victim’s browser when interacting with the vulnerable router’s web interface. This can lead to session hijacking, theft of sensitive information, or unauthorized actions performed on behalf of the user. For organizations, this could mean compromised network devices that serve as gateways, potentially allowing attackers to pivot into internal networks or disrupt network configurations. While the vulnerability does not directly allow remote code execution on the device or full system compromise, the ability to manipulate the router’s web interface can undermine network security and user trust. The medium severity reflects the limited but meaningful risk, especially in environments where the DSL-6641K is widely deployed. The exploit requires user interaction, which somewhat limits mass exploitation but targeted attacks remain feasible. The absence of known exploits in the wild suggests a window for proactive mitigation before widespread abuse occurs. Organizations relying on this hardware should consider the risk to their network perimeter and user endpoints, as successful exploitation could facilitate broader attacks or data leakage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:53 UTC

Technical details

References

Community reviews

Related threats