CyberSecBulletin
CVE-2025-14300NVD status: Modified

Tapo C200: Missing Authentication for Critical Functionality

Published Updated By the CyberSecBulletin desk

CVE-2025-14300 is a high-severity missing authentication for critical functionality vulnerability in Tapo C200 from TP-Link, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions V3_1.4.5 Build 251104, V5_1.4.6 Build 260709 Rel.27675n as the first without the flaw, so updating Tapo C200 to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.37% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Tapo C200 to V3_1.4.5 Build 251104 or V5_1.4.6 Build 260709 Rel.27675n, whichever matches your release line, or a later version.
  2. Update Tapo C100 v5 to V5_1.4.4 Build 260303 or a later version.
  3. Update Tapo C425 v1.2 to V1.20_1.2.27 Build 260518 or a later version.
  4. Read the advisory on tp-link.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
TP-LinkTapo C200before V3_1.4.5 Build 251104; before V5_1.4.6 Build 260709 Rel.27675nV3_1.4.5 Build 251104, V5_1.4.6 Build 260709 Rel.27675n
TP-LinkTapo C100 v5before V5_1.4.4 Build 260303V5_1.4.4 Build 260303
TP-LinkTapo C425 v1.2before V1.20_1.2.27 Build 260518V1.20_1.2.27 Build 260518
TP-LinkTapo C200 Firmware1.3.3; 1.3.4; 1.3.5; 1.3.7; 1.3.9; 1.3.11; 1.3.13; 1.3.14; and 4 more rangesNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.08.7HighCNA
CVSS 3.18.1HighNVD

Official description

The HTTPS service on Tapo C200 v3, v5, C425 v1.2 and C100 v5 exposes a connectAP interface without proper authentication. An unauthenticated attacker on the same local network segment can exploit this to modify the device’s Wi-Fi configuration, resulting in loss of connectivity and denial-of-service (DoS).

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authentication for Critical Functionality

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
  • When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.

More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Missing Authentication for Critical Functionality vulnerabilities

Spotted an error? Tell us.