# CVE-2025-53713: TP-Link TL-WR841N WlanNetworkRpm_APC.htm buffer overflow

> Remote attackers can cause a denial-of-service crash in the web service of unsupported TP-Link TL-WR841N routers via buffer overflow.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2025
- **Updated:** 29 Jul 2025
- **Also known as:** GHSA-rvj2-pqhh-hgg7

## What is CVE-2025-53713?

CVE-2025-53713 is a medium-severity memory corruption vulnerability in TP-Link Systems INC. TL-WR841N V11, published on 29 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-53713?

It affects 1 product.


Products: Tp-Link Tl-Wr841n Firmware.

## How do I fix CVE-2025-53713?

No fix has been published for CVE-2025-53713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53713 being exploited?

There is no known exploitation of CVE-2025-53713 in the wild and no public exploit code.

## Other vulnerabilities in TP-Link Systems INC. TL-WR841N V11

- [CVE-2022-25073](https://insights.sbomify.com/CVE-2022-25073/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-12575](https://insights.sbomify.com/CVE-2018-12575/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-46912](https://insights.sbomify.com/CVE-2022-46912/): File upload in n/a (high 8.8)
- [CVE-2020-35576](https://insights.sbomify.com/CVE-2020-35576/): Command injection in n/a (high 8.8)
- [CVE-2019-17147](https://insights.sbomify.com/CVE-2019-17147/): Memory corruption in TL-WR841N (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53713 and fix it if it is affected.

What it is: CVE-2025-53713 is a medium-severity memory corruption vulnerability in TP-Link Systems INC. TL-WR841N V11, published on 29 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53713 in the wild and no public exploit code.

Affected product: TP-Link Systems INC. TL-WR841N V11. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53713/ (Markdown: https://insights.sbomify.com/CVE-2025-53713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53713
- OSV: https://osv.dev/vulnerability/CVE-2025-53713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53713/
Summaries are generated and may contain mistakes; the official description above is the record.