dbcve.org
Archer C7 FirmwareOperating system · Tp Link

CVE-2023-39224

HIGH · 8.0 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 230602 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 C5 firmware all versions and Archer C7 firmware versions prior to 'Archer C7(JP)_V2_230602' allow a network-adjacent authenticated attacker to execute arbitrary OS commands. Note that Archer C5 is no longer supported, therefore the update for this product is not provided.

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 C7 router firmware versions prior to 'Archer C7(JP)_V2_230602' and all Archer C5 versions contain a command injection vulnerability in the web management interface. A network-adjacent attacker with valid admin credentials can inject and execute arbitrary OS commands through insufficient input validation in the firmware's administrative functions.

MitigationFor Archer C7 devices, update to firmware version 'Archer C7(JP)_V2_230602' or later. The Archer C5 is end-of-life with no patch available—replace the device with a supported model.

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 C7 FirmwareOperating system
Affected:< 230602

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 your device model
    Check the router label or web interface for the exact model number (Archer C7 or Archer C5)
    Affected if Device is a TP-Link Archer C7 or Archer C5
  2. Check Archer C7 firmware version
    Access the router web management interface (typically at 192.168.0.1) and navigate to System Tools > Firmware Upgrade, or check the label on the device for the firmware version
    Affected if Archer C7 firmware version is below 230602 (versions prior to Archer C7(JP)_V2_230602)
  3. Check Archer C5 firmware version
    Access the router web management interface and navigate to System Tools > Firmware Upgrade to view the current firmware version
    Affected if Device is an Archer C5 (all versions are affected)
  4. Assess web management interface exposure
    Determine if the router's web interface is accessible from the WAN/internet side (typically port 80/443), or only from the local LAN
    Affected if Web management interface is exposed to network-adjacent attackers (not just localhost/LAN)
  5. Verify admin credential security
    Check if the admin password has been changed from the default (default admin credentials are often admin/admin or admin/password)
    Affected if Using default or easily guessable admin credentials

You are affected if you have an Archer C7 with firmware below 230602, or any Archer C5, with the web management interface accessible to network-adjacent attackers who may obtain admin credentials.

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

For Archer C7 devices, update to firmware version 'Archer C7(JP)_V2_230602' or later. The Archer C5 is end-of-life with no patch available—replace the device with a supported model.

Recommended fix High confidence

Archer C7(JP)_V2_230602 or later

  1. 1. Identify the exact TP-Link Archer model (C7 or C5)
  2. 2. For Archer C7: Download firmware version 230602 or later from the official TP-Link support website (www.tp-link.com)
  3. 3. Access the router's web management interface by entering the router's IP address in a browser
  4. 4. Log in with administrator credentials
  5. 5. Navigate to System Tools > Firmware Upgrade
  6. 6. Upload the downloaded firmware file and wait for the upgrade to complete
  7. 7. Do not power off the router during the upgrade process
  8. 8. After reboot, verify the firmware version in the router settings
Caveat Firmware upgrade may reset router configuration to defaults; backup settings before upgrading if possible

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

Fix this in Archer C7 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-39224 — 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-39224 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