CVE-2025-4441
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-605L 2.13B01. It has been classified as critical. This affects the function formSetWAN_Wizard534. The manipulation of the argument curTime leads to buffer overflow. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure. 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 confidenceA buffer overflow vulnerability exists in D-Link DIR-605L firmware 2.13B01 within the formSetWAN_Wizard534 function. The overflow is triggered through manipulation of the curTime argument, allowing remote attackers to potentially execute arbitrary code. The vulnerability carries a CVSS 9.8 rating due to its network exploitability and critical impact.
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= 2.13b01CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label on the router or access the web interface and look for the model number displayed on the login page or status pageAffected if The device is not a D-Link DIR-605L - if different model, this CVE does not apply
-
Check the firmware versionLog into the router web interface, navigate to Status or System settings page, and locate the firmware version field. Alternatively, check the download file or release notes if you have access to the firmware image fileAffected if The firmware version is 2.13B01 - this is the exact affected version
-
Verify the web interface is accessibleAttempt to access the router's web interface by entering the router's IP address in a web browser. The vulnerable function formSetWAN_Wizard534 is part of the web administration interfaceAffected if The web interface is accessible on the network - the vulnerability is in this web function
-
Confirm WAN wizard feature existsThe vulnerability is in the formSetWAN_Wizard534 function. Check if the WAN setup wizard feature is present in the web interface under WAN or Internet settingsAffected if The WAN wizard functionality exists and is accessible - this is the vulnerable component
You are affected if you have a D-Link DIR-605L router running firmware version 2.13B01 and its web interface is accessible on your network.
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.
dbcve · scopedSince D-Link DIR-605L is end-of-life and no longer receives security updates, the primary mitigation is to replace the affected device with a currently supported router model or consider alternative firmware such as OpenWrt if hardware capabilities permit.
- The D-Link DIR-605L firmware version 2.13B01 is affected by a critical buffer overflow vulnerability (CVE-2025-4441, CVSS 9.8) in the formSetWAN_Wizard534 function.
- This product is end-of-life and no longer supported by D-Link according to the official vulnerability description.
- Replace the affected D-Link DIR-605L device with a currently supported router from D-Link or another manufacturer.
- If the device cannot be immediately replaced, place it behind a properly configured firewall and restrict network access to trusted users only to reduce attack surface.
- Monitor the device vendor for any future security advisories, though none are currently expected for this end-of-life product.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4441 — 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-4441 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