dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-70219

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
Stack buffer overflow vulnerability in D-Link DIR-513 v1.10 via the goform/formDeviceReboot.

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 confidence

A stack buffer overflow vulnerability exists in D-Link DIR-513 wireless router firmware version 1.10, specifically in the goform/formDeviceReboot form handler. The vulnerability allows stack memory corruption which can be exploited for remote code execution, as reflected by the critical CVSS score of 9.8.

MitigationSince the DIR-513 is an end-of-life device with no available firmware patches, immediate mitigation requires disabling remote web management interfaces, isolating the device behind a firewall, or replacing with a supported router model.

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
Dir 513 FirmwareOperating system
Affected:= 1.10

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Log into the router web interface or check the device label/marketing to confirm it is a D-Link DIR-513 model.
    Affected if The device is not a D-Link DIR-513, then this specific CVE does not apply.
  2. Check the firmware version
    In the router web interface, navigate to the Status or System Information page to view the firmware version. Alternatively, check via CLI if telnet/ssh is available.
    Affected if The firmware version is exactly 1.10, the device is vulnerable to this CVE.
  3. Verify the web management interface is accessible
    Confirm the router web interface (HTTP/HTTPS on ports 80/443) is reachable from the network segment you are checking. This can be done by attempting to access the router's IP address from a browser or using a network scan tool.
    Affected if The formDeviceReboot handler is only exposed when the web management interface is active, regardless of whether it is local or remote.
  4. Confirm the formDeviceReboot endpoint exists
    Attempt to access the path /goform/formDeviceReboot on the router's web server (e.g., http://[router-ip]/goform/formDeviceReboot). A 404 response indicates the endpoint may not exist or is not loaded, while a valid response indicates the handler is present.
    Affected if The endpoint returns any response other than 404, confirming the vulnerable form handler is exposed.

The device is affected if it is a D-Link DIR-513 running firmware version 1.10 with the web management interface and formDeviceReboot endpoint accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the DIR-513 is an end-of-life device with no available firmware patches, immediate mitigation requires disabling remote web management interfaces, isolating the device behind a firewall, or replacing with a supported router model.

Recommended fix Moderate confidence
  1. Disable the router's remote web management interface, limiting access to the LAN only.
  2. Block inbound HTTP/HTTPS (ports 80/443) at the external firewall or edge device to prevent external attackers from reaching the goform/formDeviceReboot endpoint.
  3. If remote management is required, use a VPN or IP‑whitelist to restrict access to trusted sources.
  4. Change the default admin credentials and ensure strong passwords are used.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 513 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-70219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-70219 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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