dbcve.org
Archer A10 FirmwareOperating system · Tp Link

CVE-2023-38568

HIGH · 8.8 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 230504 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 A10 firmware versions prior to 'Archer A10(JP)_V2_230504' allows a network-adjacent unauthenticated 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

TP-Link Archer A10 router firmware contains a pre-authentication command injection vulnerability allowing a network-adjacent unauthenticated attacker to execute arbitrary OS commands. The vulnerability is exploitable without credentials from a network-adjacent position, giving the attacker full system-level control over the device.

MitigationUpgrade Archer A10 firmware to version 'Archer A10(JP)_V2_230504' or later. If immediate patching is not possible, restrict network access to trusted users via firewall rules or network segmentation to reduce the attack surface.

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 A10 FirmwareOperating system
Affected:< 230504

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 firmware version
    Access the router's web administration interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to the Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the administration interface for a 'System' or 'Device Info' section that displays the firmware version.
    Affected if The displayed firmware version number is lower than 230504 (for example, 230420, 221525, etc.)
  2. Confirm network accessibility
    Verify that the router's management interface is reachable from the network segment where an attacker would be positioned. This can be done by attempting to access the router's IP address from a computer on the same local network.
    Affected if The router's admin interface is accessible from an untrusted network segment or the internet without firewall restrictions.

If the router's firmware version is below 230504 and the management interface is reachable from a network-adjacent position, the device is affected by this vulnerability.

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

Upgrade Archer A10 firmware to version 'Archer A10(JP)_V2_230504' or later. If immediate patching is not possible, restrict network access to trusted users via firewall rules or network segmentation to reduce the attack surface.

Recommended fix High confidence

Archer A10(JP)_V2_230504

  1. 1. Download the firmware 'Archer A10(JP)_V2_230504' from the official TP-Link support website (www.tp-link.com)
  2. 2. Connect your computer to the Archer A10 router via Ethernet cable
  3. 3. Open a web browser and access the router's web management interface at http://tplinkwifi.net or http://192.168.0.1
  4. 4. Log in to the router administration panel with administrator credentials
  5. 5. Navigate to 'System' > 'Firmware Upgrade' or 'Advanced' > 'System' > 'Firmware Upgrade'
  6. 6. Click 'Browse' or 'Choose File' and select the downloaded firmware file (Archer A10(JP)_V2_230504)
  7. 7. Click 'Upgrade' or 'Update' to begin the firmware installation
  8. 8. Wait for the upgrade process to complete - do not power off the router during this process
Caveat Firmware upgrade may reset some settings to defaults; reconfigure any custom settings after upgrade

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

Fix this in Archer A10 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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