dbcve.org
Dir 513 FirmwareOperating system · Dlink

CVE-2025-6882

HIGH · 8.8 CVSS v3.1 Published 2025-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 classified as critical has been found in D-Link DIR-513 1.0. This affects an unknown part of the file /goform/formSetWanPPTP. The manipulation of the argument curTime leads to buffer overflow. It is possible to initiate the attack 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

Buffer overflow in D-Link DIR-513 router's /goform/formSetWanPPTP CGI script. The curTime parameter is not properly validated before use in a memory buffer, allowing remote attackers to overflow the buffer and potentially execute arbitrary code. Attack is remote and requires no authentication.

MitigationDevice is end-of-life with no patch available. Replace with a currently supported router. If immediate replacement is not possible, restrict administrative access to the device from untrusted networks using firewall rules.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 and firmware version
    Access the router's web interface (typically at 192.168.0.1) and check the status/firmware page, or use telnet/ssh to access the device and run 'cat /proc/version' or check /etc/firmware_version
    Affected if Device is a D-Link DIR-513 running firmware version 1.0
  2. Confirm the vulnerable CGI script exists
    Attempt to access http://[router-ip]/goform/formSetWanPPTP via HTTP request (note: the script may respond with an error or require parameters)
    Affected if The /goform/formSetWanPPTP endpoint is reachable and responds to requests
  3. Verify PPTP WAN configuration is accessible
    Log into the router web interface and navigate to WAN settings > PPTP connection settings, or inspect the router's configuration file for PPTP-related parameters
    Affected if PPTP WAN functionality is enabled or configurable on the device
  4. Check if the router admin interface is exposed to untrusted networks
    Review firewall rules: run 'iptables -L -n' on the device or check external network accessibility of ports 80/443 to the router's WAN IP
    Affected if The router's administrative web interface (port 80/443) is accessible from WAN (untrusted) networks

You are affected if you own a D-Link DIR-513 router running firmware version 1.0 and its administrative interface or PPTP WAN feature is accessible, since the vulnerability requires no authentication to exploit the curTime parameter overflow in the formSetWanPPTP CGI script.

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

Device is end-of-life with no patch available. Replace with a currently supported router. If immediate replacement is not possible, restrict administrative access to the device from untrusted networks using firewall rules.

Recommended fix High confidence
  1. Replace the D-Link DIR-513 router with a currently supported model, as D-Link has confirmed this device is no longer supported and will not receive a firmware patch.
Caveat Discontinue use of D-Link DIR-513 hardware; replace with a currently supported router from D-Link or another vendor

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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