CVE-2025-60572
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 · uneditedD-Link DIR600L Ax FW116WWb01 was discovered to contain a buffer overflow via the curTime parameter in the function formAdvNetwork.
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 DIR600L Ax firmware FW116WWb01 where the curTime parameter in the formAdvNetwork function fails to properly validate input length before copying data into a fixed-size buffer. This allows an attacker to overwrite adjacent memory and potentially achieve remote code execution by sending specially crafted HTTP requests with oversized curTime values.
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= 1.16wwb01CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 firmware version is 1.16wwb01Access the router's web administration interface and navigate to the Status or System section to view the firmware version, or use the router's command line if available to check the firmware build informationAffected if The installed firmware version is exactly 1.16wwb01
-
Verify the device model is DIR-600LCheck the device label or web interface for the exact model number (DIR-600L Ax or similar variant)Affected if The device is a D-Link DIR-600L model
-
Check if HTTP management interface is exposedAttempt to access the router's web interface on the WAN IP using HTTP (port 80) from an external network, or review firewall rules to see if port 80/443 is forwarded or open to the internetAffected if The router's web management interface is accessible from the WAN/internet
-
Confirm formAdvNetwork function is presentInspect HTTP requests sent to the router's web interface or examine the firmware binary for the formAdvNetwork function if you have access to the firmware fileAffected if The formAdvNetwork function handles the curTime parameter in the router's HTTP request processing
You are affected if you have a D-Link DIR-600L router running firmware version 1.16wwb01 with its web management interface accessible (especially from the WAN side), as the buffer overflow in the formAdvNetwork function's curTime parameter handling can then be exploited.
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 the DIR600L is an end-of-life device with no vendor patches available, mitigate by disabling remote management access, placing the device behind a firewall with strict ACLs limiting management interface access to trusted IPs only, or replacing the device with a currently supported router.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60572 — 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-60572 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