dbcve.org
Tl Wr841n FirmwareOperating system · Tp Link

CVE-2025-53713

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/WlanNetworkRpm_APC.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 (/userRpm/WlanNetworkRpm_APC.htm) due to missing input validation on parameters passed to this wireless network configuration page. The overflow can crash the embedded web server, causing a denial-of-service condition exploitable remotely without authentication.

MitigationSince the affected device is end-of-life and no longer supported by the vendor, apply compensating controls: restrict remote HTTP/HTTPS access to the device using firewall rules, or disable the affected wireless AP client feature if not required, or replace the EOL device with a supported model.

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. Confirm device model is TP-Link TL-WR841N V11
    Access the router web interface and check the device information page, or look at the physical device label for the model number
    Affected if Device is a TL-WR841N V11 hardware version
  2. Check firmware version
    Log into the router web interface and navigate to System Tools > Firmware Upgrade (or similar) to view the current firmware version number
    Affected if Firmware version is 160325 or earlier
  3. Verify wireless AP client feature is enabled
    Navigate to Wireless > Wireless Settings (or WDS/APC settings) in the router web interface and check if the AP Client mode is enabled
    Affected if Wireless AP client feature is configured and active
  4. Confirm remote HTTP access to the router is possible
    Attempt to access the router from an external network by accessing the WAN IP on ports 80 or 443, or check the router's Remote Management settings under Security or Administration
    Affected if Remote management is enabled and the router is accessible from WAN on HTTP/HTTPS ports

A user is affected if they have a TL-WR841N V11 with firmware version 160325 or earlier, with the wireless AP client feature enabled, and with remote HTTP access exposed to the WAN.

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 the affected device is end-of-life and no longer supported by the vendor, apply compensating controls: restrict remote HTTP/HTTPS access to the device using firewall rules, or disable the affected wireless AP client feature if not required, or replace the EOL device with a supported model.

Recommended fix High confidence
  1. Since TP-Link TL-WR841N V11 is explicitly stated as a product no longer supported by the maintainer, no firmware upgrade or patch is available from the vendor.
  2. If continued use is required, consider deploying a separate firewall or intrusion prevention system between the device and the network to mitigate remote exploitation.
  3. Replace the end-of-life device with a currently supported router model that receives security updates from the manufacturer.
Caveat The affected product (TL-WR841N V11) is end-of-life and no longer supported; there is no official firmware upgrade path

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

Fix this in Tl Wr841n Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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