CVE-2025-15605: high-severity vulnerability in TP-Link Systems Inc. Archer NX200 v1.0
Hardcoded Cryptographic Key in Configuration Encryption Mechanism on TP-Link Archer NX200, NX210, NX500 and NX600
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.5epss 0.1%
A hardcoded cryptographic key within the configuration mechanism on TP-Link Archer NX200, NX210, NX500 and NX600 enables decryption and re-encryption of device configuration data. An authenticated attacker may decrypt configuration files, modify them, and re-encrypt them, affecting the confidentiality and integrity of device configuration data.
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
TP-Link Systems Inc. · Archer NX200 v1.0TP-Link Systems Inc. · Archer NX200 v2.0TP-Link Systems Inc. · Archer NX200 v2.20TP-Link Systems Inc. · Archer NX200 v3.0TP-Link Systems Inc. · Archer NX210 v2.0 v2.20TP-Link Systems Inc. · Archer NX210 v3.0TP-Link Systems Inc. · Archer NX500 v1.0TP-Link Systems Inc. · Archer NX500 v2.0TP-Link Systems Inc. · Archer NX600 v1.0TP-Link Systems Inc. · Archer NX600 v2.0TP-Link Systems Inc. · Archer NX600 v3.0Related CVEs — TP-Link Systems Inc. Archer NX200 v1.0
In the same product, most dangerous first.
CVE-2025-15517HIGHAuthorization Bypass in HTTP Server Endpoints on TP-Link Archer NX200, NX210, NX500 and NX600EPSS 3.1%CVE-2025-15519HIGHCommand Injection in Modem Management CLI on TP-Link Archer NX200, NX210, NX500 and NX600EPSS 0.6%CVE-2025-15518HIGHCommand Injection in Wireless Control CLI on TP-Link Archer NX200, NX210, NX500 and NX600EPSS 0.6%
References
https://www.tp-link.com/en/support/download/archer-nx200/#Firmwarehttps://www.tp-link.com/en/support/download/archer-nx210/#Firmwarehttps://www.tp-link.com/en/support/download/archer-nx500/#Firmwarehttps://www.tp-link.com/en/support/download/archer-nx600/#Firmwarehttps://www.tp-link.com/us/support/faq/5027/