CVE-2025-15605
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTP-Link Archer NX200, NX210, NX500, and NX600 routers contain a hardcoded cryptographic key in their configuration backup/restore mechanism. This allows an authenticated attacker to decrypt existing configuration files, inject malicious modifications, and re-encrypt them for upload back to the device, compromising both confidentiality and integrity of device settings.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3.0< 1.4.0< 1.5.0< 1.3.0< 1.3.0< 1.3.0< 1.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router modelCheck the device label on the router or log into the web interface and look at the status or system information page to confirm the exact model (Archer NX200, NX210, NX500, or NX600).Affected if The model is one of the four affected models: NX200, NX210, NX500, or NX600.
-
Check installed firmware versionLog into the router web interface, navigate to the Status or System settings page, and record the firmware version displayed. Alternatively, access the router via SSH or telnet if enabled and run commands like `cat /etc/version` or `nvram get firmware_version` to retrieve the version.Affected if The firmware version falls within the affected ranges: NX600 < 1.3.0 or < 1.4.0; NX500 < 1.5.0 or < 1.3.0; NX210 < 1.3.0; NX200 < 1.3.0 or < 1.8.0.
-
Verify configuration backup/restore is accessibleLog into the router administration interface and locate the configuration backup or restore function (typically found under System, Administration, or Backup settings). Confirm you can access this feature with administrator credentials.Affected if You have authenticated access to the router and the configuration backup/restore feature is present and enabled.
-
Inspect firmware for hardcoded cryptographic materialIf you have access to the firmware binary (downloadable from TP-Link support), examine it for static cryptographic keys using strings analysis or a hex editor. Look for hardcoded key material used in config encryption routines.Affected if A hardcoded cryptographic key is found embedded in the firmware binary rather than being uniquely derived per device.
You are affected if you are running a TP-Link Archer NX200, NX210, NX500, or NX600 router with a firmware version below the specified thresholds and the configuration backup/restore mechanism is accessible with administrative credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.01.4.01.5.0
Replace hardcoded cryptographic keys with securely generated unique keys per device, implement proper key derivation functions, and rotate keys in firmware updates.
Archer NX600: firmware >= 1.4.0 | Archer NX500: firmware >= 1.5.0 | Archer NX210: firmware >= 1.3.0 | Archer NX200: firmware >= 1.8.0
- 1. Identify your exact TP-Link Archer model number (NX200, NX210, NX500, or NX600)
- 2. Check your current firmware version through the router's web management interface (typically at 192.168.0.1) under System > Firmware Upgrade or similar
- 3. Download the appropriate fixed firmware from the official TP-Link support website for your specific model
- 4. Back up your current router configuration if possible
- 5. Upload and install the new firmware through the web interface or TP-Link Tether mobile app
- 6. Wait for the firmware to flash and the device to reboot completely
- 7. After reboot, verify the new firmware version is installed and reconfigure wireless settings if needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15605 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data