dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-70223

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

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 firmware in the curTime parameter of the goform/formAdvNetwork web interface endpoint, allowing remote code execution with CRITICAL severity (CVSS 9.8).

MitigationIsolate affected devices on restricted network segments; contact D-Link for firmware update; if no patch available, replace 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 D-Link DIR-513 device on network
    Locate the device by checking device inventory, network scans, or physical label on the router. Confirm the model number reads DIR-513.
    Affected if The device model is D-Link DIR-513
  2. Check firmware version
    Access the router web interface (typically at 192.168.0.1) and navigate to Status or System settings to view the firmware version. Alternatively, check via CLI if telnet/ssh is enabled or inspect firmware file if dumped.
    Affected if Firmware version is exactly 1.10
  3. Confirm web interface is enabled
    Attempt to access the router login page at the default gateway IP address. Verify the page loads and the goform/formAdvNetwork endpoint responds.
    Affected if The web management interface is accessible and the /goform/formAdvNetwork endpoint exists and responds to requests
  4. Check network exposure of web interface
    Verify whether the web interface is exposed to untrusted networks (WAN side) or only to trusted LAN segments. Check port forwarding rules and WAN interface accessibility on ports 80/443.
    Affected if The router web interface is accessible from an untrusted network segment

You are affected if you have a D-Link DIR-513 router running firmware version 1.10 with the web interface accessible (especially from untrusted networks) and the /goform/formAdvNetwork endpoint is present.

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

Isolate affected devices on restricted network segments; contact D-Link for firmware update; if no patch available, replace device with a supported model.

Recommended fix Moderate confidence
  1. 1. Identify if the D-Link DIR-513 device is still in production or supported by checking D-Link's product lifecycle database.
  2. 2. If the device is End-of-Life (EOL), which is likely for this legacy device (released ~2012), replacement with a currently supported router is the recommended remediation.
  3. 3. If the device cannot be immediately replaced, implement network-level mitigations: place the device behind a firewall with strict inbound access controls, disable remote management interfaces exposed to the internet, and monitor for suspicious traffic patterns.
  4. 4. Restrict physical and network access to the device's management interface to trusted users only.
  5. 5. Check D-Link's official support pages (www.dlink.com, www.dlink.com.cn) periodically for any emergency firmware releases that may be published after this CVE.
Caveat DIR-513 is likely End-of-Life (EOL) with no firmware updates available; device replacement may be necessary

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 / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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