Popup Maker <= 1.18.0 - Cross-Site Request Forgery via init
Strategic Overview
- Status
- Patched in 1.18.1
- Affected Plugin
- Popup Maker – Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder
- Affected Version
<= 1.18.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Popup Maker WordPress plugin, affecting versions <= 1.18.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.18.1; sites on affected versions should update now. Disclosed March 2023.
Vulnerability Overview
The Popup Maker plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.18.0. This is due to missing or incorrect nonce validation on the 'init' function. This makes it possible for unauthenticated attackers to flush the popup cache via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Popup Maker <= 1.18.0 carries this weakness at init, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Popup Maker the fix is 1.18.1: builds <= 1.18.0 are affected, anything from 1.18.1 onward is not.
Remediation
Update to version 1.18.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Popup Maker: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Popup Maker 1.18.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Popup Maker – Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder
- 8.8Freemius SDK <= 2.2.3 Arbitrary Options Update
- 7.5CVE-2019-17574: Popup-Maker <= 1.8.12 information disclosure
CVE-2019-17574 - 7.2CVE-2026-28177: Popup Maker Stored XSS
CVE-2026-28177 - 7.2CVE-2026-8848: Popup Maker Authenticated (Editor+) Arbitrary Plugin
CVE-2026-8848 - 6.4CVE-2025-9490: Popup Maker <= 1.20.6 Stored Cross-Site Scripting
CVE-2025-9490 - 6.4CVE-2025-4205: Popup Maker <= 1.20.4 Stored Cross-Site Scripting
CVE-2025-4205 - 6.4CVE-2025-24746: Popup Maker <= 1.20.2 Stored Cross-Site Scripting
CVE-2025-24746 - 6.4CVE-2024-7054: Popup Maker <= 1.19.0 Stored Cross-Site Scripting
CVE-2024-7054
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C