WP Popup Builder <= 1.2.9 - Missing Authorization and Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.3.0
- Affected Plugin
- WP Popup Builder – Popup Forms and Marketing Lead Generation
- Affected Version
<= 1.2.9- CVSS
- 7.5High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-2405
At a glance
CVE-2022-2405 is a high-severity Missing Authorization vulnerability in the WP Popup Builder WordPress plugin, affecting versions <= 1.2.9. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.3.0; sites on affected versions should update now. Disclosed September 2022, reported by Krzysztof Zając.
Vulnerability Overview
The WP Popup Builder plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.2.9. This is due to missing or incorrect nonce validation and capabilities checks on several of its functions available to unauthenticated users. This makes it possible for unauthenticated attackers to create, update, and delete popups.
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, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Reaching this weakness in WP Popup Builder <= 1.2.9 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 WP Popup Builder the fix is 1.3.0: builds <= 1.2.9 are affected, anything from 1.3.0 onward is not.
Remediation
Update to version 1.3.0, 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: WP Popup Builder 1.3.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Popup Builder – Popup Forms and Marketing Lead Generation
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C