Popup Builder <= 3.63 - Unauthenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.64.1
- Affected Version
<= 3.63- CVSS
- 8.3High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2020-10196
At a glance
CVE-2020-10196 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Popup Builder WordPress plugin, affecting versions <= 3.63. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.64.1; sites on affected versions should update now. Disclosed March 2020, reported by Ram.
Vulnerability Overview
An XSS vulnerability in the popup-builder plugin before 3.64.1 for WordPress allows remote attackers to inject arbitrary JavaScript into existing popups via an unsecured ajax action in com/classes/Ajax.php. It is possible for an unauthenticated attacker to insert malicious JavaScript in several of the popup's fields by sending a request to wp-admin/admin-ajax.php with the POST action parameter of sgpb_autosave and including additional data in an allPopupData parameter, including the popup's ID (which is visible in the source of the page in which the popup is inserted) and arbitrary JavaScript which will then be executed in the browsers of visitors to that page. Because the plugin functionality automatically adds script tags to data entered into these fields, this injection will typically bypass most WAF applications.
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.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Popup Builder <= 3.63 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Popup Builder the fix is 3.64.1: builds <= 3.63 are affected, anything from 3.64.1 onward is not.
Remediation
Update to version 3.64.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Popup Builder 3.64.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 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 - 6.4CVE-2024-30184: Popup Builder <= 4.2.6 Stored Cross-Site Scripting
CVE-2024-30184 - 6.1CVE-2023-6000: Popup Builder <= 4.2.2 Stored Cross-Site Scripting
CVE-2023-6000
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.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 - 7.2CVE-2022-0228: Popup Builder <= 4.0.6 SQL Injection
CVE-2022-0228
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C