Archer NX600 v3.0: Missing Authentication for Critical Functionality
CVE-2025-15517 is a high-severity missing authentication for critical functionality vulnerability in Archer NX600 v3.0 from TP-Link, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited from the same local network by an unauthenticated attacker, 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 2.95% chance of exploitation within 30 days, higher than 87% of scored 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
- NoneNo account or login is needed.
- 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:N/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.6 | High | CNA |
| CVSS 3.1 | 8.1 | High | NVD |
Official description
A missing authentication check in the HTTP server on TP-Link Archer NX200, NX210, NX500 and NX600 to certain cgi endpoints allows unauthenticated access intended for authenticated users. An attacker may perform privileged HTTP actions without authentication, including firmware upload and configuration operations.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
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.3 High severity
- 7.2 High severity
- 7.2 High severity
Recent Missing Authentication for Critical Functionality vulnerabilities
- 8.6 High severity
- 9.1 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.