dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-70236

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

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-based buffer overflow vulnerability exists in D-Link DIR-513 v1.10 routers in the goform/formSetDomainFilter form handler. The curTime parameter is copied into a fixed-size stack buffer without proper bounds checking, allowing an attacker to overflow the buffer and potentially execute arbitrary code with elevated privileges.

MitigationApply vendor firmware updates when available; if no update exists, consider network segmentation to limit exposure and monitor for exploitation attempts, as this device may be end-of-life.

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
    Access the router admin interface or check the device label to confirm the model is D-Link DIR-513
    Affected if Device is not a D-Link DIR-513 unit
  2. Check firmware version
    Log into the router web interface (typically at 192.168.0.1) and navigate to Status or System settings to view the firmware version, or use the command 'cat /proc/version' if SSH/telnet access is available
    Affected if Firmware version is 1.10
  3. Verify web management interface is enabled
    Confirm the router's HTTP/HTTPS web interface is accessible on the LAN or WAN interface by attempting to reach the login page
    Affected if Web interface is disabled and not accessible
  4. Confirm formSetDomainFilter handler exists
    Check if the router responds to requests at /goform/formSetDomainFilter - this is typically part of Domain Filter/Parental Control settings. Submit a benign request to test endpoint availability
    Affected if The formSetDomainFilter endpoint does not exist or is not functional
  5. Check if Domain Filter feature is enabled
    In the router web interface, locate the Domain Filter or Parental Control section under Security or Access Control settings and verify if this feature is active
    Affected if Domain Filter feature is enabled and accepts user input including the curTime parameter

A user is affected if they have a D-Link DIR-513 router running firmware version 1.10 with the web interface and Domain Filter (formSetDomainFilter) feature enabled, as this creates the condition where the curTime parameter can trigger the buffer overflow.

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

Apply vendor firmware updates when available; if no update exists, consider network segmentation to limit exposure and monitor for exploitation attempts, as this device may be end-of-life.

Recommended fix Moderate confidence

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

  1. 1. Visit the official D-Link support page at www.dlink.com to check for available firmware updates for the DIR-513 device.
  2. 2. Navigate to the DIR-513 product support page and locate the firmware download section.
  3. 3. If a firmware version newer than 1.10 is available, download the firmware file.
  4. 4. Access the DIR-513 web management interface via its default IP address (typically 192.168.0.1).
  5. 5. Navigate to the 'System' or 'Management' section and locate the 'Firmware Upgrade' or 'Update' option.
  6. 6. Upload the downloaded firmware file and initiate the upgrade process.
  7. 7. Wait for the firmware upload and installation to complete - do not power off the device during this process.
  8. 8. After the device reboots, verify the firmware version has been updated in the web interface.
Caveat Firmware upgrades on older D-Link devices may reset configuration to defaults; back up 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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