CVE-2025-60562
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 formWlSiteSurvey.
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 confidenceA buffer overflow vulnerability exists in the D-Link DIR600L Ax firmware (FW116WWb01) within the formWlSiteSurvey function. The curTime parameter lacks proper bounds checking, allowing an attacker to inject excess data into a fixed-size buffer and potentially execute arbitrary code or cause denial of service.
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 device model is D-Link DIR600LCheck the device label or access the web interface and look for the model number in the status or system information pageAffected if Device model is not DIR600L
-
Identify firmware versionAccess the router's web administration panel, typically at 192.168.0.1, and navigate to the Status or System section to view the firmware version. Alternatively, check the firmware file name if you have access to the firmware binaryAffected if Firmware version is 1.16wwb01 (FW116WWb01)
-
Verify web interface is accessibleAttempt to access the router's web interface on the default IP address (192.168.0.1) over HTTP/HTTPS. The vulnerability exists in the formWlSiteSurvey function within the web interfaceAffected if Web management interface is exposed and accessible on the local network or remotely
-
Check for wireless site survey functionalityNavigate to the Wireless settings section in the web interface and look for a Site Survey or WPS function that queries available wireless networks. This is where the vulnerable formWlSiteSurvey function is calledAffected if The wireless site survey feature exists and accepts user input through the curTime parameter
A user is affected if they have a D-Link DIR600L router running firmware version 1.16wwb01 (FW116WWb01) with the web interface accessible and the wireless site survey feature enabled, as the buffer overflow resides in the formWlSiteSurvey function handling the curTime parameter.
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, the primary remediation is to replace the device with a supported model or implement strict network segmentation to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60562 — 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-60562 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