CVE-2025-7945
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 · uneditedA vulnerability was found in D-Link DIR-513 up to 20190831. It has been declared as critical. This vulnerability affects the function formSetWanDhcpplus of the file /goform/formSetWanDhcpplus. The manipulation of the argument curTime leads to buffer overflow. The attack can be initiated remotely. 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 · moderate confidenceBuffer overflow vulnerability in D-Link DIR-513 router firmware (versions up to 20190831) in the formSetWanDhcpplus function. The curTime argument is not properly validated before use in a memory operation, allowing remote attackers to overflow a buffer and potentially execute arbitrary code. The vulnerability is exploitable remotely with network access to the affected device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is D-Link DIR-513Access the router web interface (typically 192.168.0.1) or check the device label to verify the exact model number matches DIR-513Affected if Device is not a D-Link DIR-513 router
-
Check firmware versionIn the router web interface, navigate to the Status or System section and locate the firmware version string; compare it numerically to 20190831Affected if Firmware version is 20190831 or earlier (any version up to and including that date)
-
Identify formSetWanDhcpplus function exposureIn the router web interface, look under WAN or Internet connection settings for a DHCP Plus or WAN DHCP Plus configuration option; this function must be present and accessible for the vulnerability to be triggeredAffected if WAN DHCP Plus configuration option exists and is accessible in the web interface
-
Assess network accessibilityCheck the router WAN status to determine if the device is directly reachable from external networks or behind a firewall/NAT; the vulnerability requires network access to the deviceAffected if Router WAN interface is exposed to untrusted networks without firewall protection
The device is affected if it is a D-Link DIR-513 router running firmware version 20190831 or earlier, with the WAN DHCP Plus feature accessible and network exposure to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataSince D-Link DIR-513 is end-of-life and no longer supported, no vendor patch is available. Recommended remediation is to replace the affected device with a currently-supported model. If immediate replacement is not feasible, restrict network access to the device by placing it behind a firewall or isolating it from untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7945 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7945 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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