dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-8184

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-26
Fix available
A fix is available. Upgrade to after 1.10 or later.
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
A vulnerability was found in D-Link DIR-513 up to 1.10 and classified as critical. This issue affects the function formSetWanL2TPcallback of the file /goform/formSetWanL2TPtriggers of the component HTTP POST Request Handler. The manipulation leads to stack-based buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

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

A stack-based buffer overflow vulnerability exists in the D-Link DIR-513 router's HTTP POST request handler for WAN L2TP configuration. The formSetWanL2TPcallback function in /goform/formSetWanL2TPtriggers fails to properly validate input length before copying data to a stack buffer, allowing remote attackers to overflow the stack and potentially execute arbitrary code. The CVSS 9.8 score indicates trivial exploitability with potential for complete system compromise.

MitigationThis vulnerability affects an end-of-life product that no longer receives security updates from the vendor. Organizations should immediately isolate the device from untrusted networks, restrict administrative access to trusted IPs only, and replace with a currently supported router. There is no vendor-supplied patch available.

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.0, <= 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's web管理界面 (typically at 192.168.0.1) and navigate to the status or system information page to identify the exact model number. Alternatively, check the physical device label on the router chassis.
    Affected if The device is not a D-Link DIR-513 model, then it is not affected by this specific CVE.
  2. Check firmware version is within vulnerable range
    In the router's web管理界面, go to Status or System Settings and locate the firmware version field. Compare the installed version against the affected range: >= 1.0 and <= 1.10.
    Affected if The firmware version falls within 1.0 through 1.10 inclusive, indicating the device may be affected.
  3. Verify L2TP VPN functionality is accessible
    Navigate to the router's WAN or VPN settings section in the web管理界面. Look for L2TP or L2TP VPN configuration options. The vulnerability exists in the formSetWanL2TPcallback function within /goform/formSetWanL2TPtriggers endpoint.
    Affected if L2TP VPN configuration features are present and accessible on the device.
  4. Assess exposure of management interface
    Determine if the router's web管理界面 (HTTP/HTTPS on ports 80/443) is reachable from external networks or the internet. Check router firewall rules, port forwarding settings, or perform an external port scan of the router's WAN IP on ports 80/443.
    Affected if The management interface is exposed to untrusted networks, allowing remote attackers to reach the vulnerable HTTP POST handler.

A D-Link DIR-513 router running firmware version 1.0 through 1.10 with an exposed management interface and accessible L2TP VPN settings is vulnerable to remote code execution via the formSetWanL2TPcallback function.

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
Upgrade available Upgrade to a release after 1.10
Interim mitigation

This vulnerability affects an end-of-life product that no longer receives security updates from the vendor. Organizations should immediately isolate the device from untrusted networks, restrict administrative access to trusted IPs only, and replace with a currently supported router. There is no vendor-supplied patch available.

Recommended fix High confidence
  1. 1. Immediately isolate the D-Link DIR-513 device from the network or place it behind a restrictive firewall to limit exposure to remote attackers.
  2. 2. Since D-Link DIR-513 is End-of-Life (EOL) and no longer supported by the vendor, no firmware patches are available for this vulnerability.
  3. 3. Replace the EOL DIR-513 device with a currently supported router that receives regular security updates.
  4. 4. If immediate replacement is not possible, disable the WAN L2TP functionality on the device via its web administration interface to reduce the attack surface.
  5. 5. Implement network segmentation to place the affected device in a restricted VLAN with minimal trust and no access to internal sensitive resources.
Caveat This is an EOL product with no available firmware updates; the only remediation path is device replacement.

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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