dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-70239

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-03
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/formSetWAN_Wizard55.

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

A stack buffer overflow vulnerability exists in D-Link DIR-513 router firmware v1.10 within the web interface's formSetWAN_Wizard55 handler. The curTime parameter is copied to a fixed-size stack buffer without proper bounds checking, allowing an attacker to overwrite return addresses and potentially achieve remote code execution.

MitigationSince D-Link DIR-513 is end-of-life with no available patch, immediate mitigation involves disabling remote web management, placing the device behind a firewall with restrictive access controls, or replacing with a supported device.

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. Confirm device model is D-Link DIR-513
    Access the router web interface (typically 192.168.0.1 or 192.168.1.1) and navigate to the Status or Device Info page to identify the exact model number
    Affected if The device model is not D-Link DIR-513, this specific vulnerability does not apply
  2. Verify firmware version is 1.10
    In the router web interface, check the firmware version under Status or Administration > Firmware Upgrade page. The affected version is specifically 1.10
    Affected if The installed firmware version equals 1.10, the specific version affected by this CVE
  3. Confirm web management interface is accessible
    Attempt to access the router web interface from the network segment where the router is deployed. The vulnerable handler formSetWAN_Wizard55 is part of the web server
    Affected if The web interface is accessible and the formSetWAN_Wizard55 handler responds to requests, enabling the attack surface
  4. Check if remote web management is enabled
    In the router web UI, navigate to Administration > Remote Management or similar settings to see if remote access to the web interface is permitted
    Affected if Remote web management is enabled, allowing unauthenticated or low-privilege attackers to reach the vulnerable handler from outside the local network

The environment is affected if the device is a D-Link DIR-513 running firmware version 1.10 with the web interface (particularly formSetWAN_Wizard55) accessible to the attacker.

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 D-Link DIR-513 is end-of-life with no available patch, immediate mitigation involves disabling remote web management, placing the device behind a firewall with restrictive access controls, or replacing with a supported device.

Recommended fix Moderate confidence

D-Link DIR-513 firmware version later than 1.10 (check D-Link support for latest available version)

  1. 1. Visit the official D-Link support page at www.dlink.com or your regional D-Link site (e.g., www.dlink.com.cn) to check for firmware updates.
  2. 2. Search for the DIR-513 router model and look for the firmware download section.
  3. 3. Download the latest available firmware version for the DIR-513.
  4. 4. Access the router's web management interface (typically at 192.168.0.1 or 192.168.1.1).
  5. 5. Navigate to the System or Administration section of the web interface.
  6. 6. Look for a Firmware Upgrade or Router Upgrade option.
  7. 7. Upload the downloaded firmware file and initiate the upgrade process.
  8. 8. Wait for the upgrade to complete and the router to reboot.
Caveat Firmware upgrades may reset router configuration to defaults; backup current settings before upgrading 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
  • 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-70239 — 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-70239 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