Popup Builder – Create highly converting, mobile friendly marketing popups <= 4.3.1 - Missing Authorization and Nonce Exposure
Strategic Overview
- Status
- Patched in 4.3.2
- Affected Version
<= 4.3.1- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-6696
At a glance
CVE-2023-6696 is a high-severity Missing Authorization vulnerability in the Popup Builder WordPress plugin, affecting versions <= 4.3.1. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.3.2; sites on affected versions should update now. Disclosed June 2024, reported by Lucio Sá.
Vulnerability Overview
The Popup Builder – Create highly converting, mobile friendly marketing popups. plugin for WordPress is vulnerable to unauthorized access of functionality due to a missing capability check on several functions in all versions up to, and including, 4.3.1. While some functions contain a nonce check, the nonce can be obtained from the profile page of a logged-in user. This allows subscribers to perform several actions including deleting subscribers and perform blind Server-Side Request Forgery.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.
CWE-862: Missing Authorization
Reaching this weakness in Popup Builder <= 4.3.1 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Popup Builder the fix is 4.3.2: builds <= 4.3.1 are affected, anything from 4.3.2 onward is not.
Remediation
Update to version 4.3.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Popup Builder 4.3.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Popup Builder – Create highly converting, mobile friendly marketing popups.
- 9.8CVE-2022-0479: Popup Builder <= 4.1.0 SQL Injection
CVE-2022-0479 - 9.8CVE-2020-9006: Popup Builder 2.2.8 - 2.6.7.6 PHP Object Injection
CVE-2020-9006 - 9.8CVE-2019-14695: Popup Builder <= 3.44 SQL Injection
CVE-2019-14695 - 8.8CVE-2022-29495: Popup Builder CSRF to Settings Update
CVE-2022-29495 - 8.8CVE-2021-25082: Popup Builder <= 4.0.6 LFI and PHAR Deserialization
CVE-2021-25082 - 8.3CVE-2020-10196: Popup Builder <= 3.63 Stored Cross-Site Scripting
CVE-2020-10196 - 7.2CVE-2022-0228: Popup Builder <= 4.0.6 SQL Injection
CVE-2022-0228 - 6.4CVE-2025-9856: Popup Builder Stored XSS
CVE-2025-9856
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C