cve.bz

CVE-2025-14300 tp-link tapo c200 firmware

8.7 highEPSS 0.4%

High (8.7) in tp-link tapo c200 firmware. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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).

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

8.1 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-12-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-306 Missing Authentication for Critical Functionality
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-14300 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-14300?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-14300?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-14300 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-14300

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-14300](https://cve.bz/cve/badge/CVE-2025-14300.svg)](https://cve.bz/cve/CVE-2025-14300)

HTML:

<a href="https://cve.bz/cve/CVE-2025-14300"><img src="https://cve.bz/cve/badge/CVE-2025-14300.svg" alt="CVE-2025-14300"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. Tapo C200before V3_1.4.5 Build 251104
TP-Link Systems Inc. Tapo C200before V5_1.4.6 Build 260709 Rel.27675n
TP Link Systems Inc. Tapo C100 v5before V5_1.4.4 Build 260303
TP Link Systems Inc. Tapo C425 v1.2before V1.20_1.2.27 Build 260518

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON