dbcve.org
Archer Ax3000 FirmwareOperating system · Tp Link

CVE-2024-21833

HIGH · 8.8 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 →
93/100
Remediation priority · Urgent
No privileges 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 unauthenticated attacker with access to the product to execute arbitrary OS commands. The affected device, with the initial configuration, allows login only from the LAN port or Wi-Fi.

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

Multiple TP-LINK devices contain an unauthenticated command injection vulnerability in their web management interface. A network-adjacent attacker without credentials can send specially crafted requests to execute arbitrary OS commands on the affected device, likely through improper input sanitization in web service parameters.

MitigationApply vendor-provided firmware updates when available; until then, restrict network access to management interfaces by placing devices in isolated network segments and disabling remote administration features.

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
Deco X50 FirmwareOperating system
Affected:< 1.4.1
Deco Xe200 FirmwareOperating system
Affected:< 1.2.5
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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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
    Locate the device label on the router or mesh unit, or access the web management interface and look for the model name (e.g., Archer AX3000, Deco X50)
    Affected if The device is not one of the listed affected models (Archer AX3000, Archer AX5400, Deco X50, Deco Xe200, Archer AXE75)
  2. Determine the installed firmware version
    Access the web management interface via browser (typically http://tplinkwifi.net or http://192.168.0.1), log in, and navigate to the firmware or system settings to find the current firmware version. Alternatively, check via the TP-Link Tether app under device settings.
    Affected if The firmware version is below the threshold for your model: Archer AX3000/Ax5400 < 1.1.2, Deco X50 < 1.4.1, Deco Xe200 < 1.2.5, Archer AXE75 < 1.1.9
  3. Verify web management interface accessibility
    Attempt to access the web management interface from a computer on the same network by navigating to http://tplinkwifi.net or http://192.168.0.1. Check if the interface responds.
    Affected if The web management interface is reachable from the network, indicating the web service is active and potentially exploitable
  4. Check if remote management or cloud access is enabled
    In the web management interface, look for settings such as 'Remote Management', 'Cloud Access', 'TP-Link ID', or 'Remote Upgrade' under Advanced or System settings. Check if these are enabled.
    Affected if Remote management or cloud-based administration features are enabled, allowing potential attackers on the network to reach the vulnerable web interface

You are affected if you have an listed TP-LINK device model running firmware below the specified version threshold, with the web management interface accessible on your network.

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 / 1.2.5 or later
Fixed in 1.1.21.1.91.2.5
Interim mitigation

Apply vendor-provided firmware updates when available; until then, restrict network access to management interfaces by placing devices in isolated network segments and disabling remote administration features.

Recommended fix High confidence

Archer Ax3000/Ax5400: 1.1.2+ | Deco X50: 1.4.1+ | Deco Xe200: 1.2.5+ | Archer Axe75: 1.1.9+

  1. Identify the TP-LINK device model from the affected list: Archer Ax3000, Archer Ax5400, Deco X50, Deco Xe200, or Archer Axe75
  2. Navigate to the official TP-LINK support website at www.tp-link.com
  3. Search for your specific device model and locate the Firmware Downloads section
  4. Download the latest firmware version: For Archer Ax3000/Ax5400, download version 1.1.2 or later; For Deco X50, download version 1.4.1 or later; For Deco Xe200, download version 1.2.5 or later; For Archer Axe75, download version 1.1.9 or later
  5. Access the device web management interface via a browser on a device connected to the LAN or Wi-Fi
  6. Locate the Firmware Upgrade or System Tools section in the management interface
  7. Upload the downloaded firmware file and initiate the upgrade process
  8. Wait for the upgrade to complete and the device to reboot
Caveat Firmware upgrades on consumer routers typically do not have breaking changes but may reset configuration to factory defaults; backup current settings before upgrading if possible

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

Fix this in Archer Ax3000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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