CVE-2025-14300: Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 & C425
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).
Security readout for executives and security teams
Plain-English summary
Affected TP-Link Tapo cameras can have their Wi-Fi settings changed by an unauthenticated person already connected to the same local network. This can disconnect cameras and interrupt monitoring. The issue is high severity, but the supplied evidence does not establish internet-based exploitation or observed attacks in the wild.
Executive priority
Prioritize identification and firmware remediation where these cameras support security monitoring, safety, or business operations. Immediate attention is warranted on shared or weakly segmented networks because exploitation requires no credentials. Treat isolated devices as urgent maintenance rather than evidence of an internet-wide emergency.
Technical view
CVE-2025-14300 is a CWE-306 authentication failure in the HTTPS connectAP interface on specified Tapo hardware revisions. An adjacent-network attacker needs no privileges or user interaction and can modify Wi-Fi configuration, causing denial of service. It carries CVSS 4.0 score 8.7.
Likely exposure
Exposure is limited to Tapo C200 v3 and v5, C425 v1.2, and C100 v5 devices reachable from an attacker-controlled client on the same local network segment. Exact vulnerable and fixed firmware versions are not included in the supplied bundle, so hardware and firmware must be checked against TP-Link guidance.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. That does not prove exploitation has never occurred. The adjacent-network requirement reduces remote exposure, while unauthenticated, low-complexity access increases risk on shared, guest-accessible, or poorly segmented networks.
Researcher notes
The narrative identifies affected hardware revisions, but the structured affected data contains placeholder version values of "0" and defaults to unaffected. This inconsistency prevents a reliable firmware boundary from being stated. Consult the vendor FAQ and model-specific release notes. The supplied evidence supports Wi-Fi configuration modification and availability loss, not broader compromise claims.
Mitigation direction
Identify affected camera models, hardware revisions, and installed firmware versions.
Review TP-Link FAQ 4849 and the release notes matching each device and region.
Install vendor-provided fixed firmware when confirmed by the applicable TP-Link guidance.
Isolate cameras from guest, BYOD, and other untrusted local-network clients.
Restrict camera management access to trusted administrative devices and networks.
Validation and detection
Inventory Tapo C100 v5, C200 v3/v5, and C425 v1.2 devices.
Compare recorded firmware versions with the matching TP-Link regional release notes.
Confirm affected cameras cannot be reached from guest or other untrusted network segments.
After remediation, verify authorized testing shows connectAP rejects unauthenticated requests.
Monitor for unexpected Wi-Fi changes or unexplained camera disconnections.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.