Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | While no CVSS score or EPSS value has been published, this vulnerability carries inherently high real-world risk due to its characteristics: the attack vector is network (CLI access over management port), the required privilege level is administrative (reducing attack surface to compromised or authorized accounts), the impact scope is complete (affects confidentiality, integrity, and availability), and the CWE-78 class has historically been both highly exploitable and frequently automated. The barrier to exploitation is low—command injection typically requires no advanced exploit techniques once authentication is obtained. The lack of published EPSS or CVSS vector data does not diminish the threat; rather, it suggests this is a recently disclosed or embargoed vulnerability. Given that patches are available and the vendor has published advisories, organizations should prioritize this as a medium-to-high priority remediation task, particularly for internet-facing or multi-tenant deployments where unauthorized administrative access could occur. This is not a low-real-risk scenario; it is a legitimate privilege-escalation and system-compromise vector. |
| Exploit ScenarioDerived | An authenticated attacker who has gained access to a router's administrative credentials (via phishing, credential stuffing, or insider threat) connects to the device's CLI management interface. The attacker targets the modem-management CLI command and injects a shell metacharacter sequence (e.g., command; malicious_payload) into a parameter field that is expected to receive benign input such as a modem configuration value. The router's CLI handler concatenates this untrusted input directly into a system command without sanitization, causing the injected payload to be executed with the privileges of the router's administrative process. The attacker thus achieves arbitrary command execution, potentially extracting configuration, modifying firewall rules, exfiltrating traffic logs, or pivoting to downstream network devices. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 23, 2026
A command injection vulnerability exists in the modem-management administrative CLI of TP-Link Archer NX-series routers (NX200, NX210, NX500, NX600) due to improper input handling in CLI commands. An authenticated attacker with administrative privileges can inject crafted input into vulnerable CLI parameters to execute arbitrary operating system commands, compromising the confidentiality, integrity, and availability of the device. A patch is available from TP-Link, and no public exploit or active exploitation has been confirmed at this time.
RemediationAI
Immediately upgrade affected TP-Link Archer NX-series routers to the latest patched firmware version available on the vendor support pages (https://www.tp-link.com/en/support/download/). For each model (NX200, NX210, NX500, NX600), download and install the latest firmware release, which contains fixes for the command injection flaw. Until patching is completed, restrict administrative CLI access to trusted administrative networks only, disable remote management interfaces (SSH, Telnet, HTTP admin console) if not required for operations, and monitor administrative account activity for anomalous CLI command patterns. Additionally, enforce strong, unique passwords for administrative accounts and consider implementing network segmentation to isolate management traffic from untrusted networks. After patching, verify firmware integrity and test administrative CLI functionality to ensure proper operation.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability is rooted in CWE-78 (Improper Neutralization of Special Elements used in an OS Command), a classic operating system command injection flaw. The affected TP-Link Archer NX-series devices (confirmed via CPE strings for NX200 v2.0–v3.0, NX210 v2.0–v3.0, NX500 v1.0–v2.0, and NX600 v1.0–v3.0) employ a modem-management administrative CLI that directly passes user-supplied input to system-level command execution without adequate sanitization or validation. The vulnerable CLI command accepts parameters that are concatenated into OS-level shell commands (likely via system(), exec(), or similar unsafe function calls), allowing shell metacharacters and command separators (e.g., semicolons, pipes, backticks) to break out of the intended command context and execute arbitrary code with the privileges of the router's administrative process.
Know when Archer Nx600 V3 0 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
Improper input handling in a modem-management 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.
Executive ViewAI
CVE-2025-15519 presents significant security risk, a OS command injection vulnerability rated CVSS 8.5. Successful exploitation could allow attackers to execute arbitrary code or commands on affected systems, potentially leading to full system compromise. A patch is available and should be applied as part of regular vulnerability management.
Apply vendor patch. If immediate patching is not feasible: (1) Deploy WAF rules to block injection patterns; (2) Restrict network access to affected components; (3) Enable enhanced logging for suspicious activity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
EUVD-2025-208940
GHSA-553r-96gg-xwgx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB