CVE-2026-15314

Published: Ago 04, 2026 Last Modified: Ago 07, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,1
Source: f23511db-6c3e-4e32-a477-6aa17d310630
Attack Vector: adjacent
Attack Complexity: low
Privileges Required: none
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
HIGH 7,5
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: none
Integrity: none
Availability: high

Description

AI Translation Available

Tapo P110 v1
smart Wi-Fi Plug contains an improper boundary validation vulnerability in the
handling of authenticated HTTP request bodies due to insufficient input
validation before memory copy operations. This may lead to buffer overflow condition,
causing the web service process to crash.

Successful exploitation
may cause the web service process to stop responding or restart, resulting in a
denial-of-service condition.

EPSS (Exploit Prediction Scoring System)

Trend Analysis

EPSS (Exploit Prediction Scoring System)

Prevede la probabilità di sfruttamento basata su intelligence sulle minacce e sulle caratteristiche della vulnerabilità.

EPSS Score
0,0020
Percentile
0,1th
Updated

EPSS Score Trend (Last 3 Days)

120

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Incomplete
Common Consequences
Security Scopes Affected:
Integrity Confidentiality Availability
Potential Impacts:
Modify Memory Execute Unauthorized Code Or Commands Dos: Crash, Exit, Or Restart Dos: Resource Consumption (Cpu)
Applicable Platforms
Languages: Memory-Unsafe, C, C++, Assembly
View CWE Details
Operating System

Tapo P110 Firmware by Tp-Link

Version Range Affected
To 1.1.4 (exclusive)
cpe:2.3:o:tp-link:tapo_p110_firmware:*:*:*:*:*:*:*:*
Common Platform Enumeration - Standardized vulnerability identification
https://www.tp-link.com/en/support/download/tapo-p110/v1/#Firmware-Release-Notes
https://www.tp-link.com/us/support/download/tapo-p110/v1/#Firmware-Release-Notes
https://www.tp-link.com/us/support/faq/5220/