dbcve.org
Archer Ax3000 FirmwareOperating system · Tp Link

CVE-2024-21821

HIGH · 8.0 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to 1.1.2 / 1.1.9 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
Multiple TP-LINK products allow a network-adjacent authenticated attacker with access to the product from the LAN port or Wi-Fi 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 · moderate confidence

This is an authenticated command injection vulnerability affecting multiple TP-LINK products. A network-adjacent attacker with valid credentials and access to the device via LAN port or Wi-Fi can inject and execute arbitrary operating system commands on the affected device.

MitigationApply vendor-supplied firmware patches when available; if no patch exists, isolate affected devices on restricted network segments and limit 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 Ax3000 FirmwareOperating system
Affected:< 1.1.2
Archer Ax5400 FirmwareOperating system
Affected:< 1.1.2
Archer Axe75 FirmwareOperating system
Affected:< 1.1.9

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 device model
    Access the router's web management interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to Status or Device Info page to confirm the exact model number
    Affected if Model is not TP-Link Archer AX3000, AX5400, or AXE75 - the device is not affected by this CVE
  2. Check the installed firmware version
    In the router's web interface, go to Status or System > Firmware Upgrade page and note the displayed firmware version number
    Affected if Firmware version is lower than 1.1.2 for AX3000/AX5400 models, or lower than 1.1.9 for AXE75 model - the device falls within the affected version range
  3. Verify LAN/Wi-Fi management access is enabled
    In the router's web interface, check Advanced > Network > IP Address or Administration settings to confirm the web management interface is accessible from the LAN side
    Affected if The management interface is reachable from LAN or Wi-Fi clients - an attacker with network proximity could attempt authentication
  4. Confirm Wi-Fi is enabled
    Check the wireless settings page to see if any Wi-Fi networks (2.4GHz or 5GHz) are active
    Affected if Wi-Fi is enabled and untrusted wireless clients can connect - this provides an attack vector for a network-adjacent attacker

A device is affected if it is an Archer AX3000, AX5400, or AXE75 running firmware below the specified versions AND its management interface is accessible from LAN or Wi-Fi where an attacker with valid credentials could inject commands.

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.1.2 / 1.1.9 or later
Fixed in 1.1.21.1.9
Interim mitigation

Apply vendor-supplied firmware patches when available; if no patch exists, isolate affected devices on restricted network segments and limit access to trusted authenticated users only.

Recommended fix High confidence

Archer Ax3000: upgrade to firmware 1.1.2 or later | Archer Ax5400: upgrade to firmware 1.1.2 or later | Archer Axe75: upgrade to firmware 1.1.9 or later

  1. 1. Identify the exact TP-LINK Archer model (Ax3000, Ax5400, or Axe75) from the device label
  2. 2. Access the router's web management interface by entering the LAN IP address (commonly 192.168.0.1 or 192.168.1.1) in a web browser
  3. 3. Log in with administrator credentials
  4. 4. Navigate to the 'Firmware Upgrade' or 'System' > 'Firmware Upgrade' section
  5. 5. Download the appropriate firmware from TP-LINK's official support page (www.tp-link.com) matching your model and version: Archer Ax3000 requires 1.1.2 or later, Archer Ax5400 requires 1.1.2 or later, Archer Axe75 requires 1.1.9 or later
  6. 6. In the web interface, click 'Browse' or 'Choose File' and select the downloaded firmware file
  7. 7. Click 'Upgrade' or 'Update' and wait for the process to complete (do not power off the device)
  8. 8. After reboot, verify the firmware version in the system information page
Caveat Firmware upgrade may cause temporary service interruption; configuration reset may be required on some models

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

Fix this in Archer Ax3000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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