dbcve.org
Archer C55 FirmwareOperating system · Tp Link

CVE-2023-32619

HIGH · 8.8 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 230505 / 230506 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
Archer C50 firmware versions prior to 'Archer C50(JP)_V3_230505' and Archer C55 firmware versions prior to 'Archer C55(JP)_V1_230506' use hard-coded credentials to login to the affected device, which may allow a network-adjacent unauthenticated attacker to execute an arbitrary OS command.

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

TP-Link Archer C50 and C55 routers contain hard-coded credentials in their firmware that allow any network-adjacent attacker to authenticate without credentials and execute arbitrary operating system commands on the affected device.

MitigationUpdate Archer C50 firmware to version 'Archer C50(JP)_V3_230505' or later and Archer C55 firmware to version 'Archer C55(JP)_V1_230506' or later to replace the hard-coded credentials with proper authentication mechanisms.

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 C55 FirmwareOperating system
Affected:< 230506
Archer C50 V3 FirmwareOperating system
Affected:< 230505

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 router model
    Log into the router web管理界面 or check the device label to confirm the exact model number (Archer C50 or Archer C55)
    Affected if The model is TP-Link Archer C50 V3 or Archer C55
  2. Check the installed firmware version
    Access the router web管理界面, navigate to System > Firmware Upgrade or Status page, and record the displayed firmware version number
    Affected if Firmware version is below 230505 for Archer C50 V3, or below 230506 for Archer C55
  3. Verify the device is network-accessible
    Confirm the router is powered on and connected to the network; use ping or nmap to verify the router's IP address is reachable from your local network
    Affected if The router is accessible on the network and its web management interface is exposed to untrusted segments
  4. Check for unauthenticated access capability
    Attempt to access the router's web管理界面 without credentials or use a network scanner to probe common management ports (80, 443) for an unauthenticated login page
    Affected if The web management interface is accessible without authentication from the network

You are affected if you have a TP-Link Archer C50 V3 device with firmware below 230505 or an Archer C55 device with firmware below 230506, and the router's management interface is accessible from 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 230505 / 230506 or later
Fixed in 230505230506
Interim mitigation

Update Archer C50 firmware to version 'Archer C50(JP)_V3_230505' or later and Archer C55 firmware to version 'Archer C55(JP)_V1_230506' or later to replace the hard-coded credentials with proper authentication mechanisms.

Recommended fix High confidence

Archer C50 V3: Archer C50(JP)_V3_230505 or later; Archer C55: Archer C55(JP)_V1_230506 or later

  1. 1. Identify your router model (Archer C50 V3 or Archer C55)
  2. 2. Visit the official TP-Link support page at www.tp-link.com and navigate to the Downloads section for your specific router model
  3. 3. Download the latest firmware: For Archer C50 V3, get version Archer C50(JP)_V3_230505 or later; For Archer C55, get version Archer C55(JP)_V1_230506 or later
  4. 4. Access the router's web management interface (typically at 192.168.0.1 or 192.168.1.1)
  5. 5. Navigate to System Tools > Firmware Upgrade (or similar path)
  6. 6. Upload the downloaded firmware file and wait for the upgrade to complete
  7. 7. After reboot, verify the firmware version has been updated to the fixed release
Caveat Standard firmware upgrade risks apply - ensure stable power during upgrade, backup configuration if possible, and device will reboot

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

Fix this in Archer C55 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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