HomeWordPress vulnerabilitiesIcegram Engage
Icegram Engage vulnerabilities
Icegram Engage has 13 known vulnerabilities in this database. The most recent published record is dated 1 Oct 2026.
- Known vulnerabilities
- 13
- Active installs
- 10,000+
- Latest version
- 3.1.44
- Last updated
- 24 Sep 2026
- Most recent
- 1 Oct 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 |
|---|---|---|---|---|
| PHP object injection CVE-2026-97284 | High 8.8 | Up to 3.1.31 | Fixed in a later version (latest 3.1.44) | 6 d ago |
| SQL injection CVE-2026-16087 | Medium 6.5 | Up to 3.1.42 | Fixed in a later version (latest 3.1.44) | 1 Aug 2026 |
| Cross-site scripting (XSS) CVE-2024-13482 | Medium 4.8 | Before 3.1.32 | Fixed in 3.1.32 | 15 May 2025 |
| Cross-site scripting (XSS) CVE-2024-13486 | Medium 4.8 | Before 3.1.32 | Fixed in 3.1.32 | 15 May 2025 |
| Cross-site scripting (XSS) CVE-2024-12302 | Medium 6.1 | Before 3.1.32 | Fixed in 3.1.32 | 6 Jan 2025 |
| Cross-site scripting (XSS) CVE-2023-51532 | Medium 6.5 | Up to 3.1.19 | Fixed in a later version (latest 3.1.44) | 1 Feb 2024 |
| Cross-site request forgery (CSRF) CVE-2023-52119 | Medium 4.3 | Up to 3.1.18 | Fixed in a later version (latest 3.1.44) | 5 Jan 2024 |
| Cross-site scripting (XSS) CVE-2023-2398 | Medium 6.1 | Before 3.1.12 | Fixed in 3.1.12 | 12 Jun 2023 |
| Cross-site scripting (XSS) CVE-2021-24941 | Medium 6.1 | Before 2.0.5 | Fixed in 2.0.5 | 21 Dec 2021 |
| Cross-site scripting (XSS) CVE-2021-36832 | Medium 4.8 | Up to 2.0.2 | Fixed in a later version (latest 3.1.44) | 19 Oct 2021 |
| Cross-site request forgery (CSRF) CVE-2016-10962 | Medium 6.5 | Before 1.9.19 | Fixed in 1.9.19 | 16 Sep 2019 |
| Cross-site scripting (XSS) CVE-2016-10963 | Medium 6.1 | Before 1.9.19 | Fixed in 1.9.19 | 16 Sep 2019 |
| Cross-site scripting (XSS) CVE-2019-15830 | Medium 5.4 | Before 1.10.29 | Fixed in 1.10.29 | 30 Aug 2019 |
Read the published descriptions
- CVE-2026-97284, 1 Oct 2026
- Contributor PHP Object Injection in Icegram <= 3.1.31 versions. CVE record
- CVE-2026-16087, 1 Aug 2026
- The Icegram Engage - Popups, Optins, CTAs & Lead Generation plugin for WordPress is vulnerable to second-order SQL Injection via 'messages[][id]' Parameter in all versions up to, and including, 3.1.42 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection is second-order: the malicious id value is first persisted to post meta via the save_campaign_preview() AJAX action (gated by a nonce check and edit_post capability, requiring Editor-level access or above), and only executed as SQL when a subsequent preview request triggers get_message_data() to interpolate the stored value directly into a SQL IN() clause without $wpdb->prepare() or integer casting. CVE record
- CVE-2024-13482, 15 May 2025
- The Icegram Engage WordPress plugin before 3.1.32 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-13486, 15 May 2025
- The Icegram Engage WordPress plugin before 3.1.32 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-12302, 6 Jan 2025
- The Icegram Engage WordPress plugin before 3.1.32 does not sanitise and escape some of its Campaign settings, which could allow authors and above to perform Stored Cross-Site Scripting attacks CVE record
- CVE-2023-51532, 1 Feb 2024
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Icegram Icegram Engage - WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building allows Stored XSS.This issue affects Icegram Engage - WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building: from n/a through 3.1.19. CVE record
- CVE-2023-52119, 5 Jan 2024
- Cross-Site Request Forgery (CSRF) vulnerability in Icegram Icegram Engage - WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building.This issue affects Icegram Engage - WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building: from n/a through 3.1.18. CVE record
- CVE-2023-2398, 12 Jun 2023
- The Icegram Engage WordPress plugin before 3.1.12 does not escape a parameter before outputting it back in an attribute, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin CVE record
- CVE-2021-24941, 21 Dec 2021
- The Popups, Welcome Bar, Optins and Lead Generation Plugin WordPress plugin before 2.0.5 does not sanitise and escape the message_id parameter of the get_message_action_row AJAX action before outputting it back in an attribute, leading to a reflected Cross-Site Scripting issue CVE record
- CVE-2021-36832, 19 Oct 2021
- WordPress Popups, Welcome Bar, Optins and Lead Generation Plugin - Icegram (versions <= 2.0.2) vulnerable at "Headline" (&message_data[16][headline]) input. CVE record
- CVE-2016-10962, 16 Sep 2019
- The icegram plugin before 1.9.19 for WordPress has CSRF via the wp-admin/edit.php option_name parameter. CVE record
- CVE-2016-10963, 16 Sep 2019
- The icegram plugin before 1.9.19 for WordPress has XSS. CVE record
- CVE-2019-15830, 30 Aug 2019
- The icegram plugin before 1.10.29 for WordPress has ig_cat_list XSS. CVE record
What to do if you run Icegram Engage
If you run Icegram Engage, 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 Icegram Engage vulnerabilities
Free. We email you when a new vulnerability is published for Icegram Engage, 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.