dbcve.org
Archer Ax6000 FirmwareOperating system · Tp Link

CVE-2023-40531

HIGH · 8.0 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
82/100
Remediation priority · High
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
Archer AX6000 firmware versions prior to 'Archer AX6000(JP)_V1_1.3.0 Build 20221208' allows a network-adjacent authenticated attacker to execute arbitrary OS commands.

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

The Archer AX6000 router firmware contains a command injection vulnerability that allows a network-adjacent authenticated attacker to execute arbitrary OS commands by injecting malicious commands through the web interface or API.

MitigationUpgrade the router firmware to version 'Archer AX6000(JP)_V1_1.3.0 Build 20221208' or later; until then, restrict network access to trusted, authenticated users only.

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 Ax6000 FirmwareOperating system
Affected:< 1.3.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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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 router model
    Log into the router web interface or check the device label. Confirm the model is TP-Link Archer AX6000.
    Affected if The device is an Archer AX6000 model.
  2. Check the installed firmware version
    Log into the router web interface and navigate to 'Advanced' > 'System' > 'Firmware Upgrade' or 'Administration' > 'Firmware'. Record the current firmware version displayed.
    Affected if The displayed firmware version is below 1.3.0.
  3. Verify if web management interface is accessible
    Attempt to access the router's web interface from the network by entering the router's IP address in a browser. Check if the login page loads.
    Affected if The web interface is accessible from an untrusted network segment.
  4. Confirm authentication status
    Attempt to log into the web interface with the current credentials. Note whether default credentials (admin/admin) are still in use or if they have been changed.
    Affected if The router uses default credentials or allows authentication from an untrusted network.

A user is affected if they are running TP-Link Archer AX6000 firmware versions below 1.3.0 and the web interface is accessible to untrusted or unauthenticated users.

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 or later
Fixed in 1.3.0
Interim mitigation

Upgrade the router firmware to version 'Archer AX6000(JP)_V1_1.3.0 Build 20221208' or later; until then, restrict network access to trusted, authenticated users only.

Recommended fix Moderate confidence

Archer AX6000 firmware version 1.3.0 or later (e.g., Archer AX6000(JP)_V1_1.3.0 Build 20221208)

  1. 1. Navigate to the official TP-Link support page for Archer AX6000 at www.tp-link.com
  2. 2. Locate the firmware download section for Archer AX6000
  3. 3. Download the latest firmware version 1.3.0 or later (specifically 'Archer AX6000(JP)_V1_1.3.0 Build 20221208' or newer)
  4. 4. Access the router's web management interface via a web browser
  5. 5. Navigate to System > Firmware Upgrade or similar section
  6. 6. Click the option to upload/upgrade firmware and select the downloaded file
  7. 7. Wait for the firmware upload and installation to complete - do not power off the router during this process
  8. 8. After the router reboots, verify the firmware version has been updated in the management interface

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

Fix this in Archer Ax6000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40531 — 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-2023-40531 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