CVE-2025-70220
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStack buffer overflow vulnerability in D-Link DIR-513 v1.10 via the curTime parameter to goform/formAutoDetecWAN_wizard4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stack buffer overflow vulnerability exists in D-Link DIR-513 wireless router firmware v1.10. The overflow occurs when processing the curTime parameter via the /goform/formAutoDetecWAN_wizard4 endpoint, potentially allowing remote attackers to overwrite stack memory and execute arbitrary code due to the missing bounds checking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is D-Link DIR-513Access the router web interface and check the status or system information page, or log into the admin panel and look for the device model name in the dashboard or system settings.Affected if The device model listed is not D-Link DIR-513, then this specific CVE does not apply.
-
Check firmware version is 1.10In the router web interface, navigate to Status or System Settings and locate the firmware version field. Compare this version number to the affected version 1.10.Affected if The installed firmware version is exactly 1.10, indicating this specific CVE applies to your device.
-
Verify the vulnerable endpoint existsSend an HTTP GET or POST request to http://<router_ip>/goform/formAutoDetecWAN_wizard4 using a tool like curl or a browser. A response (even an error) indicates the endpoint is present.Affected if The endpoint responds, confirming the vulnerable web form is available on the device.
-
Check network exposure of the management interfaceDetermine if the router's web interface (port 80/443) is directly accessible from the internet by checking your firewall/NAT rules, or use an external port scanner to test if ports 80 or 443 are open to public IP addresses.Affected if The management interface is exposed to untrusted networks (internet-facing), increasing the likelihood of remote exploitation.
You are affected if you have a D-Link DIR-513 router running firmware version 1.10 with the /goform/formAutoDetecWAN_wizard4 endpoint accessible, particularly if exposed to the internet.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply any vendor-supplied firmware update if available; otherwise, isolate the device behind a firewall or NAT to restrict management interface access from untrusted networks, as this device may be end-of-life with no patch forthcoming.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-70220 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data