dbcve.org
Archer C5400 FirmwareOperating system · Tp Link

CVE-2023-39935

HIGH · 8.0 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 230506 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 C5400 firmware versions prior to 'Archer C5400(JP)_V2_230506' 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 C5400 router firmware contains a command injection vulnerability allowing an authenticated, network-adjacent attacker to execute arbitrary OS commands. The vulnerability exists in the firmware versions prior to 'Archer C5400(JP)_V2_230506', likely due to insufficient input validation in the web management interface that passes user-supplied parameters to system shell commands.

MitigationUpgrade the router firmware to version 'Archer C5400(JP)_V2_230506' or later. If immediate patching is not feasible, restrict access to the router's administrative interface by placing it behind a VPN or firewall, limiting exposure to trusted network segments 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 C5400 FirmwareOperating system
Affected:< 230506

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. Confirm router model is Archer C5400
    Locate the device label on the router or access the web management interface to verify the exact model number matches 'Archer C5400'
    Affected if The router model is TP-Link Archer C5400
  2. Check installed firmware version
    Log into the router web interface and navigate to Status or System > Firmware Upgrade page to view the current firmware version, or use the command 'cat /proc/tpversion' if SSH access is available
    Affected if The displayed firmware version is lower than 230506 (e.g., 220921, 211019, etc.)
  3. Verify web management interface accessibility
    Check if the router admin interface (port 80/443) is accessible from untrusted network segments or the internet by attempting to reach the router IP from a non-local network
    Affected if The web interface is exposed to network segments beyond the trusted local network
  4. Confirm authentication requirements
    Attempt to access the router login page and verify whether default credentials (admin/admin) or unchanged credentials are in use
    Affected if Default credentials have not been changed and the router web interface is accessible to adjacent network attackers

The environment is affected if the router is an Archer C5400 running firmware version lower than 230506, with the web management interface accessible to network-adjacent attackers who could authenticate and exploit the command injection flaw.

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

Upgrade the router firmware to version 'Archer C5400(JP)_V2_230506' or later. If immediate patching is not feasible, restrict access to the router's administrative interface by placing it behind a VPN or firewall, limiting exposure to trusted network segments only.

Recommended fix Moderate confidence

Archer C5400 firmware version 230506 or later

  1. Download the firmware version 230506 or later for Archer C5400 from the official TP-Link support website
  2. Access the Archer C5400 router's web management interface through a browser
  3. Log in with administrator credentials
  4. Navigate to the System or Administration section, then locate the Firmware Upgrade option
  5. Upload the downloaded firmware file and initiate the upgrade
  6. Wait for the upgrade process to complete - do not power off the router during this process
  7. After the upgrade completes, the router will reboot automatically
  8. Verify the firmware version has been updated in the router's web interface
Caveat Firmware upgrades may temporarily disrupt network connectivity; ensure stable power during the upgrade process

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

Fix this in Archer C5400 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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