CVE-2025-14895 json
PopupKit <= 2.2.0 - Missing Authorization to Sensitive Information Disclosure and Data Deletion
published 2026-02-10 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-207190
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
The PopupKit plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.2.0. This is due to the plugin not properly verifying that a user is authorized to access the /popup/logs REST API endpoint. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read and delete analytics data including device types, browser information, countries, referrer URLs, and campaign metrics.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected products
- roxnor Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/c13bb699-f065-4065-9ea5-bb86d24e09ab?source=cve
- plugins.trac.wordpress.org /browser/popup-builder-block/tags/2.2.0/includes/Routes/Popup.php#L145
- plugins.trac.wordpress.org /browser/popup-builder-block/tags/2.2.0/includes/Routes/Popup.php#L32
- plugins.trac.wordpress.org /browser/popup-builder-block/tags/2.2.0/includes/Routes/Popup.php#L85
- research.cleantalk.org /cve-2025-14895
- plugins.trac.wordpress.org /changeset/3421671/popup-builder-block/trunk/includes/Routes/Popup.php
Sources
- CVE List CVE-2025-14895
- NVD CVE-2025-14895
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.