CVE-2025-60569
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 formSetRoute.
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 curTime parameter in the formSetRoute function fails to properly validate input length, allowing an attacker to overflow a buffer. This could potentially enable remote code execution or 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.
-
Identify the device modelAccess the device's web management interface or check the physical device label for the model number. Confirm it is a D-Link DIR600L revision Ax.Affected if The device is not a D-Link DIR600L Ax model.
-
Determine the firmware versionLog into the router's web interface and navigate to the Status or System Information page to view the firmware version. The version is displayed as FW116WWb01 or 1.16wwb01.Affected if The displayed firmware version matches 1.16wwb01 exactly.
-
Locate the firmware version via CLIIf telnet or SSH access is available, log in and run the command that displays system version information, typically 'cat /proc/version' or a vendor-specific status command.Affected if The firmware version reported is 1.16wwb01.
-
Verify formSetRoute accessibilityAttempt to access the router's web interface and locate the routing settings page where formSetRoute would be handled. This is typically under Network or Routing settings in the web GUI.Affected if The web management interface is accessible and the routing configuration feature is present.
-
Confirm the curTime parameter existsInspect HTTP requests when saving routing settings or check the device's web server configuration files (such as /etc/httpd.conf or similar) for the formSetRoute function handling the curTime parameter.Affected if The device processes the curTime parameter within formSetRoute without proper length validation.
The device is affected if it is a D-Link DIR600L Ax running firmware version 1.16wwb01 and the web management interface with routing configuration features 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 dataIf the device is still supported by D-Link, apply any available firmware updates. Otherwise, replace the end-of-life router and restrict network access to the device's management interface until replacement.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60569 — 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-60569 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