dbcve.org
Dir 600l FirmwareOperating system · Dlink

CVE-2025-60571

HIGH · 7.5 CVSS v3.1 Published 2025-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
D-Link DIR600LAx FW116WWb01 was discovered to contain a buffer overflow via the curTime parameter in the function formSetQoS.

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 confidence

A buffer overflow vulnerability exists in the D-Link DIR600LAx router firmware (FW116WWb01) within the formSetQoS function. The curTime parameter fails to properly validate input length before copying data into a fixed-size buffer, allowing an attacker to overwrite adjacent memory and potentially achieve remote code execution.

MitigationRestrict access to the device's web management interface to trusted networks only. Given the router is end-of-life with no official patch available, replace the device with a currently supported model. If replacement is not feasible, implement network segmentation and monitor for exploitation attempts.

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
Dir 600l FirmwareOperating system
Affected:= 1.16wwb01

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the router's web administration interface and check the device info page, or use Nmap to fingerprint the device and check the HTTP server header for 'DIR-600L' or similar D-Link identifiers
    Affected if The device is not a D-Link DIR-600LAx router - different models are not affected by this specific CVE
  2. Check the installed firmware version
    Log into the router's web interface and navigate to Status or System Info page to view the firmware version, or use the router's hidden status page (usually /dev_status.asp or similar) to retrieve version info
    Affected if The firmware version is NOT 1.16wwb01 - only this specific version is listed as affected
  3. Verify the web management interface is exposed
    Attempt to access the router's HTTP/HTTPS management interface from the network segment you are assessing - check if TCP ports 80 or 443 are listening and reachable
    Affected if The web interface is accessible from an untrusted network - exploitation requires sending crafted requests to the formSetQoS function via the web interface
  4. Confirm QoS feature configuration
    Log into the router and navigate to the QoS settings page (usually under Advanced or Bandwidth Management) to verify if Quality of Service settings are configurable
    Affected if The QoS feature is present and accessible - the vulnerable formSetQoS function handles QoS parameter processing, though the function exists regardless of whether QoS is actively used

A user is affected if they have a D-Link DIR-600LAx router running firmware version 1.16wwb01 with the web management interface accessible on their network, as the buffer overflow in formSetQoS can be triggered via the curTime parameter in QoS configuration requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the device's web management interface to trusted networks only. Given the router is end-of-life with no official patch available, replace the device with a currently supported model. If replacement is not feasible, implement network segmentation and monitor for exploitation attempts.

Recommended fix Moderate confidence

D-Link DIR-600L latest available firmware (check support.dlink.com for version newer than 1.16wwb01)

  1. 1. Identify the current firmware version of the D-Link DIR-600L router by accessing the web management interface at http://192.168.0.1 and checking the Status or Management section.
  2. 2. Navigate to the D-Link support page for the DIR-600L model (support.dlink.com) and locate the firmware download section.
  3. 3. Download the latest available firmware version for the DIR-600L from D-Link's official support website.
  4. 4. In the router's web management interface, go to the Tools or System section and locate the Firmware Upgrade option.
  5. 5. Upload the downloaded firmware file and wait for the upgrade process to complete - do not power off the router during this process.
  6. 6. After the router restarts, verify the new firmware version is installed and test that the QoS functionality still works correctly.
  7. 7. If no newer firmware is available from D-Link, consider replacing the device as it may be end-of-life.
Caveat Firmware upgrades on older D-Link routers may reset configuration to defaults; backup current settings before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 600l Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA8.0 h
46.0 hours of engineering $8,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60571 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60571 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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