# CVE-2025-15518: Command Injection in Wireless Control CLI on TP-Link Archer NX200, NX210, NX500 and NX600

> An authenticated administrator can execute arbitrary OS commands via crafted input in the wireless control CLI on TP-Link Archer routers.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-6mq5-gjcx-rvxq

## What is CVE-2025-15518?

CVE-2025-15518 is a high-severity command injection vulnerability in TP-Link Systems Inc. Archer NX200 v1.0, published on 23 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input handling in a wireless-control administrative CLI command on TP-Link Archer NX200, NX210, NX500 and NX600 allows crafted input to be executed as part of an operating system command. An authenticated attacker with administrative privileges may execute arbitrary commands on the operating system, impacting the confidentiality, integrity, and availability of the device.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 4 products.


Products: Tp-Link Archer Nx200 Firmware, Tp-Link Archer Nx210 Firmware, Tp-Link Archer Nx500 Firmware, Tp-Link Archer Nx600 Firmware.

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

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

## Is CVE-2025-15518 being exploited?

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

## Other vulnerabilities in TP-Link Systems Inc. Archer NX200 v1.0

- [CVE-2025-15517](https://insights.sbomify.com/CVE-2025-15517/): Authorization Bypass in HTTP Server Endpoints on TP-Link Archer NX200, NX210, NX500 and NX600 (high 8.6)
- [CVE-2025-15519](https://insights.sbomify.com/CVE-2025-15519/): Command Injection in Modem Management CLI on TP-Link Archer NX200, NX210, NX500 and NX600 (high 8.5)
- [CVE-2025-15605](https://insights.sbomify.com/CVE-2025-15605/): Hardcoded Cryptographic Key in Configuration Encryption Mechanism on TP-Link Archer NX200, NX210, NX500 and NX600 (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15518 is a high-severity command injection vulnerability in TP-Link Systems Inc. Archer NX200 v1.0, published on 23 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15518 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Archer NX200 v1.0. 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-15518/ (Markdown: https://insights.sbomify.com/CVE-2025-15518/index.md)
```

## Sources

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

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