VulnerabilityPublished 9 Mar 2026

CVE-2025-70238: CVE-2025-70238 · Stack-based Buffer Overflow

Affects CVE-2025-70238Source 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.5% chance of exploitation in 30 days – higher than 47% 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

Affected software

Product	Affected	Fixed in
GitHubakuma-qaq/cvereport/tree/main/d-link/CVE-2025-70238`pkg:github/akuma-qaq/cvereport/tree/main/d-link/CVE-2025-70238`Other threats	Affected =1.10	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, organizations should implement the following specific mitigations: 1) Restrict access to the router's management interface by disabling remote web administration or limiting it to trusted IP addresses via firewall rules. 2) Place the router management interface behind a VPN or secure management network to prevent unauthorized external access. 3) Monitor network traffic for unusual HTTP requests targeting the goform/formSetWAN_Wizard52 endpoint, especially those containing suspicious curTime parameter values. 4) Regularly audit and update router firmware to the latest available versions once a patch addressing this vulnerability is released. 5) Consider replacing affected devices with newer models that have active vendor support and security updates. 6) Employ network segmentation to isolate critical systems from vulnerable devices to limit potential impact. 7) Educate network administrators about this vulnerability and encourage prompt incident response if signs of exploitation appear. These measures go beyond generic advice by focusing on access control, monitoring, and network architecture adjustments tailored to this specific vulnerability.

Description

CVE-2025-70238 is a high-severity stack buffer overflow vulnerability affecting the D-Link DIR-513 router firmware version 1.10. The flaw exists in the handling of the curTime parameter within the goform/formSetWAN_Wizard52 endpoint, allowing remote attackers to cause a denial of service without requiring authentication or user interaction. Exploitation requires only network access to the vulnerable device, and while no known exploits are currently active in the wild, the vulnerability poses a significant risk to availability. This vulnerability is classified under CWE-121 (stack-based buffer overflow) and has a CVSS v3.1 base score of 7.5. Organizations using this router model should prioritize mitigation to prevent potential service disruption and network instability. No patches have been published yet, so network-level protections and monitoring are critical interim measures.

Impact

The primary impact of CVE-2025-70238 is on the availability of affected D-Link DIR-513 routers. Successful exploitation can cause the device to crash or reboot, resulting in network downtime and loss of connectivity for users relying on the router. This can disrupt business operations, especially for small offices or home offices that depend on this device for internet access. Since the vulnerability does not affect confidentiality or integrity, data theft or manipulation is unlikely; however, denial of service can indirectly impact operational continuity and productivity. The lack of authentication requirements means attackers can exploit the vulnerability remotely without credentials, increasing the risk of widespread attacks if the device is exposed to the internet. Organizations with large deployments of this router model may face significant operational disruptions if exploited at scale. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability becomes publicly known.

Summary

CVE-2025-70238 identifies a stack-based buffer overflow vulnerability in the D-Link DIR-513 router firmware version 1.10. The vulnerability is triggered via the curTime parameter sent to the goform/formSetWAN_Wizard52 endpoint, which is part of the router's web management interface. A buffer overflow occurs when the input data exceeds the allocated stack buffer size, potentially overwriting adjacent memory and causing unpredictable behavior. This can lead to a denial of service (DoS) by crashing the device or causing it to reboot unexpectedly. The vulnerability requires no authentication or user interaction, meaning an attacker can exploit it remotely simply by sending a crafted HTTP request to the router's management interface. The CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) indicates network attack vector, low attack complexity, no privileges or user interaction required, unchanged scope, no confidentiality or integrity impact, but high impact on availability. The vulnerability is categorized under CWE-121, which is a common weakness related to improper handling of memory buffers leading to stack corruption. Although no public exploits are known at this time, the ease of exploitation and impact on availability make this a critical concern for affected users. No official patches or firmware updates have been released yet, increasing the urgency for interim mitigations.

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

Affected software

Description

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

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats