CVE Tools

CVE-2026-15315

Unauthenticated Administrative Authentication Bypass via device_confirm Replay in TP-Link Tapo C120 and C200

No known exploitation. EPSS puts it in the 21st percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check each TP-Link Tapo C120 v1 and C200 v5 camera’s firmware version in the Tapo app or its device settings.
  2. Update Tapo C120 v1 to 1.9.3 Build 260521 or later, and Tapo C200 v5 to V5_1.4.6 Build 260709 Rel.27675n or later.
  3. Until every camera is updated, keep cameras on a private network and prevent guests or unknown devices from joining it.

What it is

From the CVE record

Tapo C120 v1 and C200 v5 contain an improper authentication vulnerability within the login authentication verification module. An attacker on the local network can exploit weaknesses in challenge parameter validation to bypass normal authentication controls and obtain administrative session tokens. Successful exploitation may allow an attacker to subsequently execute privileged management actions, enable unauthorized administrative access and temporary disruption of device services, resulting in a denial-of-service (DoS) condition.

In plain language

Written by AI from the record

This affects TP-Link Tapo C120 v1 and C200 v5 cameras: someone on your local network can take over the camera without its password, so update it promptly.

Unauthenticated administrative authentication bypass in Tapo C120 v1 and C200 v5 caused by replayable, weakly validated device_confirm challenge parameters.

If you're affected

  • Full camera takeover
  • Unauthorized settings changes
  • Camera service disruption
  • Loss of camera availability

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS21st
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 21st percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 17 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Record updatedrecord updated
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector AdjacentRequires access to the local network (e.g. same Wi-Fi, Bluetooth)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Tapo C120 Firmware, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store