Low severity · published Jun 21, 2025
CVE-2025-52916
Yealink RPS before 2025-06-04 lacks SN verification attempt limits, enabling brute-force enumeration (last five digits)
2.2
CVSS
0.3%
EPSS
No
On KEV
Description
Yealink RPS before 2025-06-04 lacks SN verification attempt limits, enabling brute-force enumeration (last five digits).
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 22% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
RP
RPS · Yealink
before 2025-06-04 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-52916
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-52916
dnip.ch
https://dnip.ch/2025/06/25/yealink-voip-phones-insecurity-by-design/
seclists.org
https://seclists.org/fulldisclosure/2025/Jun/20
support.yealink.com
https://support.yealink.com/en/portal/knowledge/show?id=6476e7cd6a27da76bd06a9c9
www.yealink.com
https://www.yealink.com/en/trust-center/security-advisories/b8dc062eaa8d4f59
More from RPS
7.4
CVE-2025-68644
Yealink RPS before 2025-06-27 allows unauthorized access to information, including AutoP URL addresses
5.0
CVE-2025-52918
Yealink RPS before 2025-05-26 does not prevent OpenAPI access by frozen enterprise accounts, allowing unauthorized access to deactivated interfaces
4.3
CVE-2025-52917
The Yealink RPS API before 2025-05-26 lacks rate limiting, potentially enabling information disclosure via excessive requests
4.3
CVE-2025-52919
In Yealink RPS before 2025-05-26, the certificate upload function does not properly validate certificate content, potentially allowing invalid certificates to be uploaded