Strategic Overview
- Status
- Patched in 4.1.1
- Affected Version
< 4.1.1- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2022-0479
At a glance
CVE-2022-0479 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Popup Builder WordPress plugin, affecting versions < 4.1.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.1.1; sites on affected versions should update now. Disclosed March 2022, reported by Krzysztof Zając.
Vulnerability Overview
The Popup Builder WordPress plugin before 4.1.1 does not sanitise and escape the sgpb-subscription-popup-id parameter before using it in a SQL statement in the All Subscribers admin dashboard, leading to a SQL injection, which could also be used to perform Reflected Cross-Site Scripting attack against a logged in admin opening a malicious 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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in Popup Builder < 4.1.1 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Popup Builder the fix is 4.1.1: builds < 4.1.1 are affected, anything from 4.1.1 onward is not.
Remediation
Update to version 4.1.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Popup Builder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Popup Builder 4.1.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Popup Builder – Create highly converting, mobile friendly marketing popups.
- 9.8CVE-2020-9006: Popup Builder 2.2.8 - 2.6.7.6 PHP Object Injection
CVE-2020-9006 - 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 - 8.1CVE-2023-6696: Popup Builder Missing Authorization and Nonce Exposure
CVE-2023-6696 - 7.4CVE-2024-2544: Popup Builder Missing Authorization in Multiple AJAX
CVE-2024-2544 - 6.4CVE-2025-9856: Popup Builder Stored XSS
CVE-2025-9856 - 6.4CVE-2024-2506: Popup Builder <= 4.2.7 Stored Cross-Site Scripting
CVE-2024-2506
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C