Archer NX600 v3.0: Use of Hard-coded Credentials
CVE-2025-15605 is a high-severity use of hard-coded credentials vulnerability in Archer NX600 v3.0 from TP-Link, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. The record lists version 1.3.0 Build 260309 as the first without the flaw, so updating Archer NX600 v3.0 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Archer NX600 v3.0 to 1.3.0 Build 260309 or a later version.
- Update Archer NX600 v2.0 to 1.3.0 Build 260311 or a later version.
- Update Archer NX600 v1.0 to 1.4.0 Build 260311 or a later version.
- Read the advisory on tp-link.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| TP-Link | Archer NX600 v3.0 | before 1.3.0 Build 260309 | 1.3.0 Build 260309 |
| TP-Link | Archer NX600 v2.0 | before 1.3.0 Build 260311 | 1.3.0 Build 260311 |
| TP-Link | Archer NX600 v1.0 | before 1.4.0 Build 260311 | 1.4.0 Build 260311 |
| TP-Link | Archer NX500 v2.0 | before < 1.5.0 Build 260309 | < 1.5.0 Build 260309 |
| TP-Link | Archer NX500 v1.0 | before 1.3.0 Build 260311 | 1.3.0 Build 260311 |
| TP-Link | Archer NX210 v3.0 | before 1.3.0 Build 260309 | 1.3.0 Build 260309 |
| TP-Link | Archer NX210 v2.0 v2.20 | before 1.3.0 Build 260311 | 1.3.0 Build 260311 |
| TP-Link | Archer NX200 v3.0 | before < 1.3.0 Build 260309 | < 1.3.0 Build 260309 |
| TP-Link | Archer NX200 v2.20 | before 1.3.0 Build 260311 | 1.3.0 Build 260311 |
| TP-Link | Archer NX200 v2.0 | before 1.3.0 Build 260311 | 1.3.0 Build 260311 |
| TP-Link | Archer NX200 v1.0 | before 1.8.0 Build 260311 | 1.8.0 Build 260311 |
| TP-Link | Archer Nx600 Firmware | before 1.3.0; before 1.4.0 | 1.3.0, 1.4.0 |
| TP-Link | Archer Nx500 Firmware | before 1.5.0; before 1.3.0 | 1.5.0, 1.3.0 |
| TP-Link | Archer Nx210 Firmware | before 1.3.0 | 1.3.0 |
| TP-Link | Archer Nx200 Firmware | before 1.3.0; before 1.8.0 | 1.3.0, 1.8.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.5 | High | CNA |
| CVSS 3.1 | 7.3 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Credentials
The product contains hard-coded credentials, such as a password or cryptographic key.
How developers prevent this class of flaw
- For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible. In Windows environments, the Encrypted File System (EFS) may provide some protection.
- For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a first login mode that requires the user to enter a unique strong password or key.
- If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
More Use of Hard-coded Credentials vulnerabilities (CWE-798)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Other vulnerabilities in Archer NX600 v3.0
- 7.2 High severity
- 7.2 High severity
- 8.1 High severity
Recent Use of Hard-coded Credentials vulnerabilities
- 9.4 Critical severity
- 8.7 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.2 High severity
- 9.8 Critical severity
Spotted an error? Tell us.