dbcve.org
Archer Nx600 FirmwareOperating system · Tp Link

CVE-2025-15518

HIGH · 7.2 CVSS v3.1 Published 2026-03-23
Fix available
A fix is available. Upgrade to 1.3.0 / 1.4.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper input handling in a wireless-control administrative CLI command on TP-Link Archer NX200, NX210, NX500 and NX600 allows crafted input to be executed as part of an operating system command. An authenticated attacker with administrative privileges may execute arbitrary commands on the operating system, impacting the confidentiality, integrity, and availability of the device.

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 confidence

Command injection vulnerability in the wireless-control administrative CLI command on TP-Link Archer NX200, NX210, NX500, and NX600 allows authenticated administrators to inject arbitrary OS commands through unsanitized input. The flaw exists in how the CLI processes input for wireless-control functions.

MitigationApply vendor firmware updates when released; until then, restrict CLI administrative access to trusted networks only and monitor for unauthorized access attempts.

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
Archer Nx600 FirmwareOperating system
Affected:< 1.3.0< 1.4.0
Archer Nx500 FirmwareOperating system
Affected:< 1.5.0< 1.3.0
Archer Nx210 FirmwareOperating system
Affected:< 1.3.0
Archer Nx200 FirmwareOperating system
Affected:< 1.3.0< 1.8.0

CVSS 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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the exact Archer model
    Check the device label, web UI status page, or CLI output for the specific model number (NX200, NX210, NX500, or NX600)
    Affected if The model is one of the four affected models listed in the CVE
  2. Determine the installed firmware version
    Access the router web interface under System > Firmware Upgrade, or use the CLI command 'show version' to retrieve the current firmware build
    Affected if The firmware version falls below the affected thresholds: 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
  3. Verify administrative CLI access is enabled
    Confirm the router's CLI is accessible via telnet, SSH, or serial connection, and that administrator credentials are configured
    Affected if The administrative CLI interface is exposed and reachable on the network
  4. Confirm wireless-control CLI command exists
    Log into the CLI and attempt to access the wireless-control command context, or check CLI command documentation for the presence of this administrative function
    Affected if The wireless-control CLI command is available to authenticated administrators

A user is affected if they have an NX200, NX210, NX500, or NX600 device running firmware below the specified version thresholds AND the administrative CLI with wireless-control functionality is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3.0 / 1.4.0 / 1.5.0 or later
Fixed in 1.3.01.4.01.5.0
Interim mitigation

Apply vendor firmware updates when released; until then, restrict CLI administrative access to trusted networks only and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Archer NX600: firmware 1.4.0 or later; Archer NX500: firmware 1.5.0 or later; Archer NX210: firmware 1.3.0 or later; Archer NX200: firmware 1.8.0 or later

  1. 1. Identify the exact model number (NX200, NX210, NX500, or NX600) of the TP-Link Archer device.
  2. 2. Determine the current firmware version installed on the device via the web management interface (System Tools > Firmware Upgrade) or CLI.
  3. 3. Access the TP-Link support page at www.tp-link.com and navigate to the Downloads/Support section for the specific model.
  4. 4. Download the latest firmware version for the device: For Archer NX600 use version 1.4.0 or later; For Archer NX500 use version 1.5.0 or later; For Archer NX210 use version 1.3.0 or later; For Archer NX200 use version 1.8.0 or later.
  5. 5. Access the device's web management interface and navigate to System Tools > Firmware Upgrade.
  6. 6. Click the button to browse and select the downloaded firmware file.
  7. 7. Click Upgrade and wait for the firmware to upload and install - do not power off the device during this process.
  8. 8. After the device reboots, verify the new firmware version is installed correctly.
Caveat Firmware upgrades may reset some configurations to defaults; backup configuration before upgrading and reapply settings after upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archer Nx600 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15518 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15518 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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