dbcve.org
Tl Wr841n FirmwareOperating system · Tp Link

CVE-2025-53715

HIGH · 7.5 CVSS v3.1 Published 2025-07-29
Fix available
A fix is available. Upgrade to after 160325 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 vulnerability has been found in TP-Link TL-WR841N V11. The vulnerability exists in the /userRpm/Wan6to4TunnelCfgRpm.htm file due to missing input parameter validation, which may lead to the buffer overflow to cause a crash of the web service and result in a denial-of-service (DoS) condition. The attack may be launched remotely. This vulnerability only affects products that are no longer supported by the maintainer.

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 buffer overflow vulnerability exists in the TP-Link TL-WR841N V11 router's web interface (Wan6to4TunnelCfgRpm.htm) due to missing input validation on parameters. Remote attackers can exploit this to overflow a buffer, crashing the web service and causing denial-of-service.

MitigationSince this affects an end-of-life product no longer supported by TP-Link, replace the affected router with a currently supported model. If continued use is unavoidable, disable the web management interface from WAN-facing exposure and restrict access to trusted LAN networks only.

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
Tl Wr841n FirmwareOperating system
Affected:<= 160325

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 your router model
    Check the device label on the router or log into the web management interface to confirm the exact model is TP-Link TL-WR841N V11
    Affected if The router is a TL-WR841N V11 model
  2. Check the installed firmware version
    Access the router's web interface, typically at 192.168.0.1, and navigate to System Tools > Firmware Upgrade or Status page to view the firmware version number
    Affected if The firmware version is 160325 or earlier
  3. Confirm the web management interface is accessible
    Attempt to reach the router's web interface from the network where the router is deployed
    Affected if The web interface at Wan6to4TunnelCfgRpm.htm is reachable and responds to requests
  4. Verify IPv6 tunneling configuration
    In the router web interface, look for IPv6 or 6to4 tunnel settings under WAN or Advanced settings to determine if this feature is enabled
    Affected if IPv6 or 6to4 tunnel configuration features are active on the device

You are affected if you have a TL-WR841N V11 router running firmware version 160325 or earlier with the web interface accessible and IPv6 tunneling features enabled.

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 a release after 160325
Interim mitigation

Since this affects an end-of-life product no longer supported by TP-Link, replace the affected router with a currently supported model. If continued use is unavoidable, disable the web management interface from WAN-facing exposure and restrict access to trusted LAN networks only.

Recommended fix High confidence

Replace with a currently supported TP-Link router model (contact TP-Link for current supported models)

  1. 1. Replace the TP-Link TL-WR841N V11 router with a currently supported model, as this device is end-of-life and no longer receives security updates from the vendor.
  2. 2. If immediate replacement is not possible, disable remote web management access (http/https) on the router's WAN interface to prevent remote exploitation.
  3. 3. Place the device behind a properly configured firewall and restrict network access to only trusted internal hosts.
  4. 4. Monitor network traffic for attempts to access /userRpm/Wan6to4TunnelCfgRpm.htm or similar web interface endpoints.
Caveat The TL-WR841N V11 is end-of-life and will not receive security patches; continued use poses unmitigated security risk

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

Fix this in Tl Wr841n Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Review / QA2.0 h
6.0 hours of engineering $1,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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