CVE-2025-60551
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 next_page parameter in the function formDeviceReboot.
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 formDeviceReboot function. The next_page parameter is not properly validated, allowing an attacker to overflow a buffer by providing excessively long input. This memory corruption could potentially allow remote code execution or cause device 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 DIR600LAccess the router web management interface (typically at 192.168.0.1) and check the status or device info page for the model number, or physically inspect the device label.Affected if The device model shows DIR600L
-
Verify firmware version is 1.16wwb01In the router web interface, navigate to the Status or Management page and locate the firmware version field. The exact location varies by firmware but is typically shown under Device Info, Status, or System settings.Affected if The displayed firmware version reads exactly 1.16wwb01 (FW116WWb01)
-
Confirm web management interface is activeAttempt to access the router login page via HTTP on the LAN or WAN interface (default 192.168.0.1). Verify the page loads and shows the D-Link login or status screen.Affected if The web interface is reachable and responds with D-Link router pages
-
Check if formDeviceReboot endpoint is accessibleSend an HTTP GET or POST request to the router's formDeviceReboot function. On affected firmware, this is typically at /goform/formDeviceReboot or similar. Use a tool like curl: curl -X POST http://192.168.0.1/goform/formDeviceRebootAffected if The endpoint responds (even with an error) indicating the function exists and is reachable
The device is affected if it is a D-Link DIR600L router running firmware version 1.16wwb01 with an accessible web management interface.
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 D-Link DIR600L is an End-of-Life product with no official security updates, replace the affected device with a currently supported router. If replacement is not possible, restrict network access to the device's web management interface to trusted sources only.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60551 — 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-60551 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