# LAN Code Execution on TP-Link Archer MR200, Archer C20, TL-WR850N and TL-WR845N

CVE record · `CVE-2025-15551`

- **Identifiers:** `CVE-2025-15551`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **CNA:** TPLink
- **Weakness (CWE):** [CWE-95](https://cwe.mitre.org/data/definitions/95.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Technologies:** [TP-Link Systems Inc. Archer MR200 v5.2](https://agentprime.io/advisories/technology/tp-link-systems-inc-archer-mr200-v5-2.md) · [TP-Link Systems Inc. Archer C20 v6](https://agentprime.io/advisories/technology/tp-link-systems-inc-archer-c20-v6.md) · [TP Link Systems Inc. TL-WR850N v3](https://agentprime.io/advisories/technology/tp-link-systems-inc-tl-wr850n-v3.md) · [TP Link Systems Inc. TL-WR845N v4](https://agentprime.io/advisories/technology/tp-link-systems-inc-tl-wr845n-v4.md) · [TP-Link Systems Inc. Archer C20 v5](https://agentprime.io/advisories/technology/tp-link-systems-inc-archer-c20-v5.md)
- **Published:** 5 Feb 2026
- **Updated:** 22 Apr 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: TPLink) at 5 Feb 2026, 17:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: TP-Link Systems Inc.. Product: Archer MR200 v5.2.
  - affected: `before 1.2.0 Build 250917 Rel.51746` (custom)
  - Other versions: unaffected
- Vendor: TP-Link Systems Inc.. Product: Archer C20 v6.
  - affected: `before 0.9.1 4.19 v0001.0 Build 250630 Rel.56583n` (custom)
  - Other versions: unaffected
- Vendor: TP Link Systems Inc.. Product: TL-WR850N v3.
  - affected: `before 3.16.0 0.9.1 v6031.0 Build 251205 Rel.22089n` (custom)
  - Other versions: unaffected
- Vendor: TP Link Systems Inc.. Product: TL-WR845N v4.
  - affected: `before 0.9.1 3.19 Build 251031 rel33710` (custom)
  - Other versions: unaffected
- Vendor: TP-Link Systems Inc.. Product: Archer C20 v5.
  - affected: `before US_V5_260419` (custom)
  - affected: `before EU_V5_260317` (custom)
  - Other versions: unaffected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.9 Medium, CVSS 4.0: `CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`, from CNA (TPLink)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0044, the 38th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 5 Feb 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2025-15551](https://www.cve.org/CVERecord?id=CVE-2025-15551)
- [NVD: CVE-2025-15551](https://nvd.nist.gov/vuln/detail/CVE-2025-15551)

### References from the CNA

- <https://www.tp-link.com/en/support/download/archer-mr200/v5.20/#Firmware> (patch)
- <https://www.tp-link.com/en/support/download/archer-c20/v6/#Firmware> (patch)
- <https://www.tp-link.com/in/support/download/tl-wr850n/#Firmware> (patch)
- <https://www.tp-link.com/en/support/download/tl-wr845n/#Firmware> (patch)
- <https://www.tp-link.com/in/support/download/archer-mr200/v5.20/#Firmware> (patch)
- <https://www.tp-link.com/in/support/download/archer-c20/v6/#Firmware> (patch)
- <https://www.tp-link.com/in/support/download/tl-wr845n/#Firmware> (patch)
- <https://www.tp-link.com/us/support/faq/4948/> (vendor-advisory)
- <https://www.tp-link.com/us/support/download/archer-c20/v5/#Firmware> (patch)
- <https://www.tp-link.com/en/support/download/archer-c20/v5/#Firmware> (patch)

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-15551>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-15551/>. Everything for agents: <https://agentprime.io/llms.txt>.