VulnerabilityPublished 18 Sep 2025

CVE-2025-10628: D-Link DIR-852 · Command Injection

Affects D-Link DIR-852Source CVE Database V5

Public exploit available · 10% EPSS · CVSS 5.3 Medium · end of life, no fix coming : replace or isolate D-Link DIR-852; no fix will be released.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 10.0% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 18 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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

No fix will be released: D-Link DIR-852 is end of life. Replace it, or isolate it from untrusted networks until you can.

AI-suggested

Since the affected product is no longer supported and no official patches exist, European organizations should prioritize the following mitigations: 1) Immediate replacement or upgrade of the D-Link DIR-852 routers to supported models with up-to-date firmware to eliminate the vulnerability. 2) If replacement is not immediately feasible, restrict remote access to the router's management interface by limiting it to trusted internal networks and disabling remote management features. 3) Implement network segmentation to isolate legacy devices from critical infrastructure and sensitive data environments. 4) Employ intrusion detection/prevention systems (IDS/IPS) to monitor for suspicious command injection attempts targeting the hedwig.cgi endpoint. 5) Regularly audit network devices to identify unsupported hardware and maintain an asset inventory to prevent unmanaged devices from remaining in production. 6) Educate IT staff about the risks of unsupported devices and the importance of timely hardware lifecycle management. These steps go beyond generic advice by focusing on compensating controls and proactive asset management in the absence of vendor patches.

Description

A vulnerability was found in D-Link DIR-852 1.00CN B09. This vulnerability affects unknown code of the file /htdocs/cgibin/hedwig.cgi of the component Web Management Interface. Performing manipulation results in command injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used. This vulnerability only affects products that are no longer supported by the maintainer.

Impact

For European organizations, the impact of this vulnerability depends largely on the continued deployment of the affected D-Link DIR-852 1.00CN B09 routers, which are no longer supported. If these devices are still in use, especially in small to medium enterprises or home office environments, attackers could remotely compromise the routers to gain unauthorized access to internal networks, intercept or manipulate traffic, or disrupt connectivity. This could lead to data breaches, loss of network availability, or serve as a foothold for further attacks within the organization. Given the medium severity and the requirement of low privileges, the threat is moderate but non-negligible. The lack of vendor support means no official patches are available, increasing the risk over time. European organizations relying on legacy network equipment without proper segmentation or monitoring are particularly vulnerable. Additionally, the public availability of an exploit increases the risk of opportunistic attacks targeting these devices.

Summary

CVE-2025-10628 is a command injection vulnerability identified in the D-Link DIR-852 router, specifically version 1.00CN B09. The vulnerability resides in the web management interface component, within the /htdocs/cgibin/hedwig.cgi file. Command injection vulnerabilities allow an attacker to execute arbitrary commands on the underlying operating system with the privileges of the affected application. In this case, the vulnerability can be exploited remotely without requiring user interaction or authentication, as indicated by the CVSS vector (AV:N/AC:L/AT:N/UI:N/PR:L). The attack complexity is low, meaning that an attacker with network access to the device can manipulate input parameters to inject commands. The CVSS 4.0 base score is 5.3, categorized as medium severity, reflecting limited impact on confidentiality, integrity, and availability (all rated low), and the requirement of low privileges (PR:L). The vulnerability affects only an unsupported version of the DIR-852 router, which reduces the likelihood of widespread exploitation but still poses risks to environments where these devices remain in use. No official patches or updates have been released, and although no exploits are currently known to be in the wild, a public exploit has been made available, increasing the risk of future attacks. The vulnerability's presence in the web management interface means that successful exploitation could allow attackers to execute arbitrary system commands, potentially leading to device compromise, network pivoting, or disruption of network services managed by the router.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 18 Sep 2025, 01:04 UTC

Technical details

References

Community reviews

Related threats