CVE-2023-40357
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 · uneditedMultiple TP-LINK products allow a network-adjacent authenticated attacker to execute arbitrary OS commands. Affected products/versions are as follows: Archer AX50 firmware versions prior to 'Archer AX50(JP)_V1_230529', Archer A10 firmware versions prior to 'Archer A10(JP)_V2_230504', Archer AX10 firmware versions prior to 'Archer AX10(JP)_V1.2_230508', and Archer AX11000 firmware versions prior to 'Archer AX11000(JP)_V1_230523'.
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 confidenceMultiple TP-LINK Archer router models contain an OS command injection vulnerability allowing a network-adjacent authenticated attacker to execute arbitrary operating system commands. The attacker needs network access to the device and valid authentication credentials to exploit this flaw.
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< 230529<= 230504< 230508< 230523CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelCheck the device label on the router or log into the web management interface and look for the model number in the status or system settings pageAffected if The model is not one of: Archer AX50, Archer A10, Archer AX10, or Archer AX11000 (these are the only affected models)
-
Check firmware versionLog into the router web interface and navigate to Status or System settings to view the current firmware version. Alternatively, check the download page or release notes for your specific modelAffected if The firmware version is below the following thresholds: AX50 < 230529, A10 <= 230504, AX10 < 230508, AX11000 < 230523
-
Verify remote management accessCheck if the router's web administration interface is accessible from the WAN/outside network. This is typically found under Advanced > Network > Internet or Security settings, or by attempting to access the router's public IP from an external networkAffected if Remote management from WAN is enabled, allowing network-adjacent attackers to reach the login page
-
Review admin account accessCheck the list of admin users in the router settings under Administration or User Management to confirm who has valid credentialsAffected if There are user accounts with weak or default credentials, or unauthorized admin accounts exist
-
Look for unexpected configuration changesCheck router logs (typically under System Tools > Logs) for unfamiliar IP addresses, repeated login attempts, or commands that you did not initiateAffected if Logs show unknown IP addresses logging in or executing commands not initiated by you
You are affected if you own an Archer AX50, A10, AX10, or AX11000 router running firmware below the specified version thresholds and the router's web interface is accessible from the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped230508230523230529
Update affected router firmware to the latest version provided by TP-LINK: Archer AX50 to version 'Archer AX50(JP)_V1_230529' or later, Archer A10 to 'Archer A10(JP)_V2_230504' or later, Archer AX10 to 'Archer AX10(JP)_V1.2_230508' or later, and Archer AX11000 to 'Archer AX11000(JP)_V1_230523' or later.
Archer AX50: version 230529+ | Archer A10: V2 version 230504+ | Archer AX10: V1.2 version 230508+ | Archer AX11000: version 230523+
- 1. Identify your exact TP-LINK Archer router model number (e.g., Archer AX50, Archer A10, Archer AX10, or Archer AX11000)
- 2. Navigate to the official TP-LINK support page at https://www.tp-link.com/
- 3. Search for your model and locate the Firmware Download section
- 4. Download the appropriate fixed firmware version: Archer AX50 to version 230529 or later, Archer A10 to version 230504 or later (V2), Archer AX10 to version 230508 or later (V1.2), or Archer AX11000 to version 230523 or later
- 5. Access your router's web management interface by entering the router's IP address in a browser
- 6. Log in with administrator credentials
- 7. Navigate to System > Firmware Upgrade (or similar menu path)
- 8. Click the option to upgrade firmware from a file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-40357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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