dbcve.org
Tapo C520ws FirmwareOperating system · Tp Link

CVE-2026-34121

HIGH · 8.8 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 1.2.4 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
An authentication bypass vulnerability within the HTTP handling of the DS configuration service in TP-Link Tapo C520WS v2.6 was identified, due to inconsistent parsing and authorization logic in JSON requests during authentication check. An unauthenticated attacker can append an authentication-exempt action to a request containing privileged DS do actions, bypassing authorization checks. Successful exploitation allows unauthenticated execution of restricted configuration actions, which may result in unauthorized modification of device state.

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 TP-Link Tapo C520WS v2.6 contains an authentication bypass in its DS configuration service HTTP handler. The vulnerability stems from inconsistent parsing and authorization logic when processing JSON requests. An unauthenticated attacker can exploit this by appending authentication-exempt actions to requests containing privileged DS do actions, bypassing the authorization checks and allowing unauthorized modification of device configuration.

MitigationApply the vendor-provided firmware patch when available. Until then, restrict network access to the device's management interface to trusted IPs only to reduce 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
Tapo C520ws FirmwareOperating system
Affected:< 1.2.4

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 device model
    Check the device label or access the device's web interface/system info to confirm the model is TP-Link Tapo C520WS
    Affected if Device is a TP-Link Tapo C520WS
  2. Check firmware version
    Access the device management interface or use the Tapo app to view device firmware version information. Alternatively, inspect the device's system settings or API endpoint that exposes firmware version.
    Affected if Firmware version is below 1.2.4 (e.g., 1.2.3, 1.2.2, etc.)
  3. Verify DS configuration service exposure
    Check if the device's DS (Device Service) configuration endpoint is accessible from the network. This typically involves probing HTTP/HTTPS ports on the device for the '/DS' or 'DS do' API endpoint.
    Affected if DS configuration service is exposed on the network without proper access controls
  4. Review authentication configuration
    Examine the device's security settings and authentication configuration to determine if the DS service allows requests without proper authentication tokens or session validation.
    Affected if DS service permits unauthenticated or improperly authenticated requests
  5. Inspect for unauthorized configuration changes
    Review device configuration logs, audit trails, or configuration change history for any modifications made without corresponding authenticated sessions or from unexpected source IPs.
    Affected if Configuration changes exist that were not performed by an authorized user with valid authentication

The device is affected if it is a TP-Link Tapo C520WS running firmware version below 1.2.4 and has its DS configuration service exposed to the 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 1.2.4 or later
Fixed in 1.2.4
Interim mitigation

Apply the vendor-provided firmware patch when available. Until then, restrict network access to the device's management interface to trusted IPs only to reduce attack surface.

Recommended fix High confidence

Firmware version 1.2.4

  1. 1. Log into the TP-Link Tapo app or web interface for the C520WS device.
  2. 2. Navigate to the device settings or firmware update section.
  3. 3. Check the current firmware version to confirm it is below 1.2.4.
  4. 4. If an update is available, download and install firmware version 1.2.4 or later.
  5. 5. Verify the firmware has been updated successfully and the device is functioning normally.

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

Fix this in Tapo C520ws Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing6.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,700
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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