HomeWordPress vulnerabilitiesPopup Builder
Popup Builder vulnerabilities
Popup Builder has 22 known vulnerabilities in this database. The most recent published record is dated 4 Jun 2026.
- Known vulnerabilities
- 22
- Active installs
- 200,000+
- Latest version
- 4.4.5
- Last updated
- 18 Jul 2026
- Most recent
- 4 Jun 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2019-25744 | Medium 5.4 | Not yet published | Check for an update | 4 Jun 2026 |
| Security weakness CVE-2025-13079 | Medium 5.3 | Up to 4.4.2 | Fixed in a later version (latest 4.4.5) | 19 Feb 2026 |
| Cross-site scripting (XSS) CVE-2025-9856 | Medium 6.4 | Up to 4.4.1 | Fixed in a later version (latest 4.4.5) | 13 Dec 2025 |
| Cross-site scripting (XSS) CVE-2024-9428 | Medium 4.8 | Before 4.3.5 | Fixed in 4.3.5 | 12 Dec 2024 |
| Sensitive data exposure CVE-2024-2541 | Medium 5.3 | Up to 4.3.3 | Fixed in a later version (latest 4.4.5) | 29 Aug 2024 |
| Cross-site scripting (XSS) CVE-2024-3236 | Medium 5.4 | Before 1.1.33 | Fixed in 1.1.33 | 17 Jun 2024 |
| Server-side request forgery (SSRF) CVE-2023-6696 | High 8.1 | Before 4.3.2 | Fixed in 4.3.2 | 15 Jun 2024 |
| Cross-site scripting (XSS) CVE-2024-2544 | High 7.4 | Before 4.3.2 | Fixed in 4.3.2 | 15 Jun 2024 |
| Cross-site scripting (XSS) CVE-2024-2506 | Medium 6.4 | Up to 4.2.7 | Fixed in a later version (latest 4.4.5) | 1 Jun 2024 |
| Server-side request forgery (SSRF) CVE-2023-6294 | High 7.2 | Before 4.2.6 | Fixed in 4.2.6 | 12 Feb 2024 |
| Cross-site scripting (XSS) CVE-2023-6000 | Medium 6.1 | Before 4.2.3 | Fixed in 4.2.3 | 1 Jan 2024 |
| Cross-site scripting (XSS) CVE-2023-3226 | Medium 4.8 | Up to 4.1.15 | Fixed in a later version (latest 4.4.5) | 25 Sep 2023 |
| Cross-site request forgery (CSRF) CVE-2022-29495 | Medium 5.4 | Before 4.1.12 | Fixed in 4.1.12 | 22 Jul 2022 |
| Cross-site request forgery (CSRF) CVE-2022-32289 | Medium 5.4 | Before 4.1.1 | Fixed in 4.1.1 | 21 Jul 2022 |
| Cross-site scripting (XSS) CVE-2022-1894 | Medium 4.8 | Before 4.1.11 | Fixed in 4.1.11 | 11 Jul 2022 |
| Cross-site scripting (XSS) CVE-2022-0479 | Critical 9.8 | Before 4.1.1 | Fixed in 4.1.1 | 28 Mar 2022 |
| SQL injection CVE-2022-0228 | High 7.2 | Before 4.0.7 | Fixed in 4.0.7 | 21 Feb 2022 |
| Remote code execution CVE-2021-25082 | High 8.8 | Before 4.0.7 | Fixed in 4.0.7 | 21 Feb 2022 |
| Privilege escalation CVE-2020-10195 | Medium 6.3 | Before 3.64.1 | Fixed in 3.64.1 | 13 Mar 2020 |
| Cross-site scripting (XSS) CVE-2020-10196 | Medium 6.1 | Before 3.64.1 | Fixed in 3.64.1 | 13 Mar 2020 |
| SQL injection CVE-2020-9006 | Critical 9.8 | Up to 2.6.7.6 | Fixed in a later version (latest 4.4.5) | 17 Feb 2020 |
| SQL injection CVE-2019-14695 | Critical 9.8 | Before 3.45 | Fixed in 3.45 | 6 Aug 2019 |
Read the published descriptions
- CVE-2019-25744, 4 Jun 2026
- WordPress Popup Builder 3.49 contains a persistent cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts by breaking out of option tags in the post_title parameter. Attackers can submit crafted POST requests to the post.php endpoint with script payloads in the post_title field that execute when pages or posts display popup selections. CVE record
- CVE-2025-13079, 19 Feb 2026
- The Popup Builder - Create highly converting, mobile friendly marketing popups. plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.4.2. This is due to the plugin generating predictable unsubscribe tokens using deterministic data. This makes it possible for unauthenticated attackers to unsubscribe arbitrary subscribers from mailing lists via brute-forcing the unsubscribe token, granted they know the victim's email address CVE record
- CVE-2025-9856, 13 Dec 2025
- The Popup Builder - Create highly converting, mobile friendly marketing popups. plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'sg_popup' shortcode in all versions up to, and including, 4.4.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-9428, 12 Dec 2024
- The Popup Builder WordPress plugin before 4.3.5 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2024-2541, 29 Aug 2024
- The Popup Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.3.6 via the Subscribers Import feature. This makes it possible for unauthenticated attackers to extract sensitive data after an administrator has imported subscribers via a CSV file. This data may include the first name, last name, e-mail address, and potentially other personally identifiable information of subscribers. CVE record
- CVE-2024-3236, 17 Jun 2024
- The Popup Builder WordPress plugin before 1.1.33 does not sanitise and escape some of its Notification fields, which could allow users such as contributor and above to perform Stored Cross-Site Scripting attacks. CVE record
- CVE-2023-6696, 15 Jun 2024
- 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. CVE record
- CVE-2024-2544, 15 Jun 2024
- The Popup Builder plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on all AJAX actions. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform multiple unauthorized actions, such as deleting subscribers, and importing subscribers to conduct stored cross-site scripting attacks. CVE record
- CVE-2024-2506, 1 Jun 2024
- The Popup Builder - Create highly converting, mobile friendly marketing popups. plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the custom JS functionality in all versions up to, and including, 4.2.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-6294, 12 Feb 2024
- The Popup Builder WordPress plugin before 4.2.6 does not validate a parameter before making a request to it, which could allow users with the administrator role to perform SSRF attack in Multisite WordPress configurations. CVE record
- CVE-2023-6000, 1 Jan 2024
- The Popup Builder WordPress plugin before 4.2.3 does not prevent simple visitors from updating existing popups, and injecting raw JavaScript in them, which could lead to Stored XSS attacks. CVE record
- CVE-2023-3226, 25 Sep 2023
- The Popup Builder WordPress plugin before 4.2.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2022-29495, 22 Jul 2022
- Cross-Site Request Forgery (CSRF) vulnerability in Sygnoos Popup Builder plugin <= 4.1.11 at WordPress allows an attacker to update plugin settings. CVE record
- CVE-2022-32289, 21 Jul 2022
- Cross-Site Request Forgery (CSRF) vulnerability in Sygnoos Popup Builder plugin <= 4.1.0 at WordPress leading to popup status change. CVE record
- CVE-2022-1894, 11 Jul 2022
- The Popup Builder WordPress plugin before 4.1.11 does not escape and sanitize some settings, which could allow high privilege users to perform Stored Cross-Site Scripting attacks when the unfiltred_html is disallowed CVE record
- CVE-2022-0479, 28 Mar 2022
- 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 CVE record
- CVE-2022-0228, 21 Feb 2022
- The Popup Builder WordPress plugin before 4.0.7 does not validate and properly escape the orderby and order parameters before using them in a SQL statement in the admin dashboard, which could allow high privilege users to perform SQL injection CVE record
- CVE-2021-25082, 21 Feb 2022
- The Popup Builder WordPress plugin before 4.0.7 does not validate and sanitise the sgpb_type parameter before using it in a require statement, leading to a Local File Inclusion issue. Furthermore, since the beginning of the string can be controlled, the issue can lead to RCE vulnerability via wrappers such as PHAR CVE record
- CVE-2020-10195, 13 Mar 2020
- The popup-builder plugin before 3.64.1 for WordPress allows information disclosure and settings modification, leading to in-scope privilege escalation via admin-post actions to com/classes/Actions.php. By sending a POST request to wp-admin/admin-post.php, an authenticated attacker with minimal (subscriber-level) permissions can modify the plugin's settings to allow arbitrary roles (including subscribers) access to plugin functionality by setting the action parameter to sgpbSaveSettings, export a list of current newsletter subscribers by setting the action parameter to csv_file, or obtain system configuration information including webserver configuration and a list of installed plugins by setting the action parameter to sgpb_system_info. CVE record
- CVE-2020-10196, 13 Mar 2020
- 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. CVE record
- CVE-2020-9006, 17 Feb 2020
- The Popup Builder plugin 2.2.8 through 2.6.7.6 for WordPress is vulnerable to SQL injection (in the sgImportPopups function in sg_popup_ajax.php) via PHP Deserialization on attacker-controlled data with the attachmentUrl POST variable. This allows creation of an arbitrary WordPress Administrator account, leading to possible Remote Code Execution because Administrators can run PHP code on Wordpress instances. (This issue has been fixed in the 3.x branch of popup-builder.) CVE record
- CVE-2019-14695, 6 Aug 2019
- A SQL injection vulnerability exists in the Sygnoos Popup Builder plugin before 3.45 for WordPress. Successful exploitation of this vulnerability would allow a remote attacker to execute arbitrary SQL commands on the affected system via com/libs/Table.php because Subscribers Table ordering is mishandled. CVE record
What to do if you run Popup Builder
If you run Popup Builder, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Popup Builder vulnerabilities
Free. We email you when a new vulnerability is published for Popup Builder, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.