Cyber Resilience

CVE-2025-14756

Command Injection in Tp-Link Archer Mr600 Firmware ≤ 1.1.0

Published
26 January 2026
Modified
09 March 2026
Patch / advisory
CVSS Score v4 8.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.027 84th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2025-14756 is a high-severity Command Injection (CWE-77) vulnerability in Tp-Link Archer Mr600 Firmware. Its CVSS base score is 8.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 16% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-14756 is a command injection vulnerability (CWE-77) discovered in the admin interface component of TP-Link Archer MR600 v5 firmware. Published on 2026-01-26, it carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw enables authenticated attackers to execute system commands via crafted input in the browser developer console, though with a limited character length.

An attacker with low-privilege authenticated access (PR:L) can exploit this vulnerability remotely over the network (AV:N) with low attack complexity (AC:L) and without requiring user interaction (UI:N). Exploitation allows injection and execution of system commands, potentially resulting in service disruption or full compromise of the affected device.

Advisories from the Japan Vulnerability Notes (JVN) provide further details at https://jvn.jp/en/vu/JVNVU94651499/ and https://jvn.jp/vu/JVNVU94651499/. TP-Link recommends applying updated firmware, available for download at https://www.tp-link.com/en/support/download/archer-mr600/#Firmware, https://www.tp-link.com/jp/support/download/archer-mr600/#Firmware, and https://www.tp-link.com/us/support/faq/4916/.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Command injection vulnerability was found in the admin interface component of TP-Link Archer MR600 v5 firmware, allowing authenticated attackers to execute system commands with a limited character length via crafted input in the browser developer console, possibly leading to service…

more

disruption or full compromise.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-1389Same vendor: Tp-Link
CVE-2023-27078Same vendor: Tp-Link
CVE-2023-43138Same vendor: Tp-Link
CVE-2023-31701Same vendor: Tp-Link
CVE-2025-15607Same vendor: Tp-Link
CVE-2021-4045Same vendor: Tp-Link
CVE-2023-33538Same vendor: Tp-Link
CVE-2023-27836Same vendor: Tp-Link
CVE-2023-27837Same vendor: Tp-Link
CVE-2023-43137Same vendor: Tp-Link

Affected Assets

tp-link
archer mr600 firmware
≤ 1.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References