dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-70226

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 curTime parameter to goform/formEasySetupWizard.

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

Stack buffer overflow vulnerability in D-Link DIR-513 v1.10 router's web interface. The vulnerability exists in the curTime parameter passed to the /goform/formEasySetupWizard endpoint, allowing an attacker to overflow a stack-based buffer and potentially execute arbitrary code with elevated privileges.

MitigationThis is a critical remote code execution vulnerability in an older embedded device. Primary mitigation is to disable remote web management access, restrict the device to a trusted local network segment, and ideally replace the end-of-life device with a currently supported 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
    Check the device label or login to the router web interface and look for the model number in the status or system information page
    Affected if The device is not a D-Link DIR-513 router, then it is not affected by this specific CVE
  2. Check the firmware version
    Login to the router web interface and navigate to the Status or System section to find the firmware version, or check the download file name if you have access to the firmware image
    Affected if The firmware version is not 1.10, then it is not affected by this CVE (only version 1.10 is listed as affected)
  3. Verify the web management interface is enabled
    Check the router settings under Administration, Management, or Remote Management to see if the web interface is enabled
    Affected if The web interface is disabled, the attack surface is reduced but the device may still be vulnerable if re-enabled
  4. Check network exposure of the web interface
    Access the router from an external IP address on port 80 or 443, or check port forwarding/NAT rules on upstream devices to see if the router's web port is accessible from untrusted networks
    Affected if The router web interface is exposed to the internet or untrusted networks, the vulnerability is remotely exploitable

The environment is affected if it contains a D-Link DIR-513 router running firmware version 1.10 with the web management interface enabled and 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

This is a critical remote code execution vulnerability in an older embedded device. Primary mitigation is to disable remote web management access, restrict the device to a trusted local network segment, and ideally replace the end-of-life device with a currently supported model.

Recommended fix Moderate confidence
  1. 1. Check D-Link support sites (www.dlink.com, www.dlink.com.cn) for any available firmware updates for the DIR-513 model.
  2. 2. If no firmware update is available, this device has likely reached end-of-life and should be replaced with a currently supported router.
  3. 3. As a temporary mitigation, place the affected device on an isolated network segment to limit exposure.
  4. 4. Disable remote management interfaces (WAN access) for the DIR-513 if not needed.
  5. 5. If the device must remain in service, monitor for any security announcements from D-Link regarding this CVE.
Caveat DIR-513 is an older device likely at end-of-life with no firmware updates expected; replacement is the recommended long-term solution

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-70226 — 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-70226 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