dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-70221

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/formLogin.

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 · moderate confidence

Stack buffer overflow in D-Link DIR-513 v1.10 router web interface. The vulnerability exists in the goform/formLogin handler when processing the curTime parameter, allowing an unauthenticated remote attacker to overflow a stack buffer and potentially achieve arbitrary code execution. The CVSS 9.8 indicates network-level exploitability with no authentication required and complete system compromise potential.

MitigationThis is an end-of-life router with no available patch. Immediately restrict or disable remote management access to the device's web interface via firewall rules or network segmentation. Strongly consider replacing the device with a 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 device model
    Check the router web interface status page or physical device label to confirm the model is D-Link DIR-513.
    Affected if Device is not a D-Link DIR-513
  2. Check installed firmware version
    Navigate to the router web interface Administration or Status page and locate the firmware version field. Compare your installed version to the affected range.
    Affected if Firmware version is 1.10
  3. Verify web interface accessibility
    Check router settings under Remote Management or Web Access configuration. Determine if the management interface can be accessed from the WAN/internet side.
    Affected if Remote management is enabled or web interface is exposed externally
  4. Assess network exposure
    Review firewall rules and port forwarding settings to determine if the router web interface ports are accessible from outside the local network.
    Affected if The router web interface is reachable from the internet

Device is affected if it is a D-Link DIR-513 running firmware version 1.10 with remote management enabled or web interface exposed to the internet.

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 an end-of-life router with no available patch. Immediately restrict or disable remote management access to the device's web interface via firewall rules or network segmentation. Strongly consider replacing the device with a supported model.

Recommended fix Moderate confidence

D-Link DIR-513 latest available firmware (check www.dlink.com.cn for version newer than 1.10)

  1. 1. Visit the official D-Link support page at www.dlink.com or www.dlink.com.cn and navigate to the DIR-513 product support area.
  2. 2. Download the latest available firmware version for the DIR-513 router.
  3. 3. Access the router's web management interface (typically at 192.168.0.1).
  4. 4. Navigate to the System or Administration section of the settings.
  5. 5. Locate the Firmware Upgrade option and select the downloaded firmware file.
  6. 6. Wait for the firmware upload and installation to complete - do not power off the device during this process.
  7. 7. After the router restarts, verify the new firmware version in the status page.
  8. 8. After upgrading, change the router admin password to mitigate credential-related attacks.
Caveat Firmware updates on older D-Link devices may reset configuration to defaults; backup settings before upgrade if possible

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

Fix this in Dir 513 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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