dbcve.org
Td W8961nd FirmwareOperating system · Tp Link

CVE-2025-15606

HIGH · 7.5 CVSS v3.1 Published 2026-03-23
Fix available
A fix is available. Upgrade to 250925 or later.
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
A Denial-of-Service (DoS) vulnerability in the httpd component of TP-Link's TD-W8961N v4.0 due to improper input sanitization, allows crafted requests to trigger a processing error that causes the httpd service to crash. Successful exploitation may allow the attacker to cause service interruption, resulting in a DoS condition.

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 · high confidence

A Denial-of-Service vulnerability exists in the httpd web server component of TP-Link TD-W8961N v4.0 routers due to improper input sanitization. Attackers can send crafted HTTP requests that trigger a processing error, causing the httpd service to crash and result in service interruption.

MitigationApply vendor-supplied firmware update when available; in the interim, disable remote web management or restrict access to the httpd service via firewall rules to block unauthenticated requests.

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
Td W8961nd FirmwareOperating system
Affected:< 250925

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
    Log into the router's web administration interface and check the device information or status page to confirm the exact model is TP-Link TD-W8961N
    Affected if The device model is not TD-W8961N v4.0 - the CVE does not apply to other models
  2. Check the installed firmware version
    In the router's web UI, navigate to System Tools > Firmware Upgrade or Status page and locate the firmware version number
    Affected if The firmware version is less than 250925 (e.g., 250912, 250801, older versions)
  3. Confirm httpd web server is accessible
    Attempt to access the router's web login page via HTTP on the configured IP address (typically 192.168.1.1) from the network
    Affected if The httpd web interface is reachable and responds to HTTP requests
  4. Check if remote web management is enabled
    In the router's web UI, go to Security > Remote Management or Advanced > Remote Access settings and verify whether remote management via HTTP/HTTPS is enabled
    Affected if Remote web management is enabled, allowing unauthenticated access to the httpd service from WAN

You are affected if you have a TP-Link TD-W8961N v4.0 router running firmware version below 250925 AND the httpd web interface is accessible (especially if remote management is enabled), as this allows attackers to crash the service with crafted HTTP 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
Upgrade available Upgrade to 250925 or later
Fixed in 250925
Interim mitigation

Apply vendor-supplied firmware update when available; in the interim, disable remote web management or restrict access to the httpd service via firewall rules to block unauthenticated requests.

Recommended fix Moderate confidence

TD-W8961N v4.0 firmware version 250925 or later

  1. Check the current firmware version of the TD-W8961N v4.0 device via the web management interface (typically at 192.168.1.1)
  2. Navigate to the firmware upgrade or system settings section
  3. Download the official firmware version 250925 or later from TP-Link's support website (www.tp-link.com) for the TD-W8961N v4.0
  4. Upload the firmware file through the web interface or use TP-Link's firmware upgrade utility
  5. Wait for the upgrade to complete and the device to reboot automatically
  6. Verify the new firmware version is installed correctly

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

Fix this in Td W8961nd Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15606 — 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-15606 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