VulnerabilityPublished 9 Mar 2026Updated 10 Mar 2026

CVE-2025-70250: D-Link DIR-513 router firmware · Stack-based Buffer Overflow

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Mar 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 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

AI-suggested

Immediately disable remote management features on the D-Link DIR-513 router to reduce exposure to external attacks.
Restrict access to the router's management interface by implementing network segmentation and firewall rules that limit access to trusted IP addresses only.
Monitor router logs and network traffic for unusual activity or repeated requests to the goform/formdumpeasysetup endpoint, which may indicate exploitation attempts.
If possible, replace affected devices with newer models that have updated firmware and security patches.
Regularly check D-Link’s official channels for firmware updates addressing this vulnerability and apply patches promptly once available.
Educate users about the risks of using outdated router firmware and encourage best practices for network device security.
Consider deploying network intrusion detection/prevention systems (IDS/IPS) that can detect and block malformed packets targeting this vulnerability.
For critical environments, implement redundant internet connectivity to mitigate the impact of potential router outages.

Description

CVE-2025-70250 is a stack buffer overflow vulnerability found in the D-Link DIR-513 router firmware version 1.10, triggered via the curTime parameter in the goform/formdumpeasysetup endpoint. This vulnerability allows remote attackers to cause a denial of service (DoS) by crashing the device without requiring authentication or user interaction. The flaw stems from improper bounds checking on input data, leading to memory corruption. Although no known exploits are currently in the wild, the vulnerability has a high CVSS score of 7.5 due to its potential to disrupt device availability. No patches have been released yet, increasing the risk for affected users. Organizations relying on this router model should be aware of the risk and implement mitigations to prevent exploitation. The vulnerability primarily impacts home and small office environments using this specific D-Link model. Countries with significant deployment of D-Link networking equipment, especially in Asia, Europe, and North America, are most likely to be affected.

Impact

The primary impact of CVE-2025-70250 is a denial of service condition caused by remote exploitation of the stack buffer overflow, leading to router crashes and network outages. This can disrupt internet connectivity for home users and small businesses relying on the D-Link DIR-513 router, potentially affecting productivity and access to critical online services. Although the vulnerability does not directly compromise confidentiality or integrity, the loss of availability can have cascading effects, including interruption of VoIP services, remote work capabilities, and IoT device connectivity. For organizations with limited IT support or those unaware of the vulnerability, prolonged downtime could result in operational disruptions. Additionally, attackers could leverage the DoS condition as part of a larger attack strategy, such as network reconnaissance or distraction during multi-stage intrusions. The absence of patches increases the window of exposure, and the ease of exploitation without authentication makes this a significant risk for affected users worldwide.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 16 Mar 2026, 19:13 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats