CVE-2025-60553
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 formSetWAN_Wizard52.
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 D-Link DIR600L Ax firmware FW116WWb01. The vulnerability is triggered through the curTime parameter in the formSetWAN_Wizard52 function, allowing an attacker to overwrite memory due to insufficient bounds checking. The critical CVSS score of 9.8 indicates potential for complete compromise of the device.
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
- 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 device modelAccess the device's web administration interface or check the device label. Look for the model number DIR-600L in the web interface under Status, System, or Device Info pages.Affected if The device is not a D-Link DIR-600L, the check does not apply.
-
Check firmware versionIn the web interface, navigate to Status or System section and locate the firmware version field. The affected version is specifically FW116WWb01 or 1.16wwb01.Affected if The installed firmware version is exactly 1.16wwb01 (FW116WWb01).
-
Verify web interface is accessibleAttempt to access the device's management interface via HTTP/HTTPS on the LAN IP address (typically 192.168.0.1). Confirm the login page loads.Affected if The web interface is reachable - this is required for exploitation.
-
Check remote administration statusIn the web interface, go to Tools > Admin or Advanced > Remote Management settings. Look for options labeled 'Remote Management', 'Remote Access', or 'Enable Web Server' that allow access from WAN.Affected if Remote administration is enabled and the management interface is exposed to WAN, the device is at higher risk of remote attack.
The device is affected if it is a D-Link DIR-600L running firmware version 1.16wwb01 (FW116WWb01) and the formSetWAN_Wizard52 function with the curTime parameter is accessible.
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 dataApply vendor-supplied firmware patches when available. Until a patch is released, restrict network access to the device's management interface and disable remote administration to reduce attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60553 — 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-60553 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