Is Icegram Engage safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.1.47). As of 2026-11-04. 18 issues are on record for older versions; version 3.1.44 or newer fixes all of them that state a fix. Keep Icegram Engage on the latest version (3.1.47) and remove it if you do not use it.

Which versions of Icegram Engage are vulnerable?

Known issues on record (newest first): PHP object injection (3.1.31 and older, fixed in 3.1.44); SQL injection (3.1.42 and older, fixed in 3.1.43); Missing authorization check (3.1.35 and older, fixed in 3.1.36); Stored cross-site scripting (XSS) (older than 3.1.32, fixed in 3.1.32); Stored cross-site scripting (XSS) (3.1.31 and older, fixed in 3.1.32); Missing authorization check (3.1.24 and older, fixed in 3.1.25). The full list with sources is on this page.

What is the latest version of Icegram Engage?

3.1.47, according to wordpress.org (last updated 2026-10-30). It has 10,000+ active installs.

What should I do if my Icegram Engage is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update icegram). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · icegram · data as of 2026-11-04

Is Icegram Engage safe? Known vulnerabilities and latest version

Latest version: 3.1.47
Last updated: 2026-10-30
Active installs: 10,000+
Known issues on record: 18
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.1+

Create high-converting popups, floating hello bars, slide-ins, opt-in forms & CTAs in minutes. Unlimited campaigns, no pageview limits & no coding. — by Icegram

What to do

Update to the latest version (3.1.47). Anything older than 3.1.44 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get icegram --field=version shows what you run; wp plugin update icegram updates it.

Check your version

Known vulnerabilities

18 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 8.8 CVE-2026-97284 · published 2026-10-01

PHP object injection in Icegram Engage (3.1.31 and older)

Affected: 3.1.31 and older
Fixed in: 3.1.44
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Contributor PHP Object Injection in Icegram <= 3.1.31 versions.

NVD CVE-2026-97284 Patchstack advisory

medium 6.5 CVE-2026-16087 · published 2026-08-01

SQL injection in Icegram Engage (3.1.42 and older)

Affected: 3.1.42 and older
Fixed in: 3.1.43 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-16087 Wordfence advisory Code change (fix)Plugin source

medium 6.5 CVE-2025-68507 · published 2026-01-22

Missing authorization check in Icegram Engage (3.1.35 and older)

Affected: 3.1.35 and older
Fixed in: 3.1.36
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in Icegram Icegram icegram allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Icegram: from n/a through <= 3.1.35.

NVD CVE-2025-68507 Patchstack advisory

medium 4.8 CVE-2024-13482 · published 2025-05-15

Stored cross-site scripting (XSS) in Icegram Engage (older than 3.1.32)

Affected: older than 3.1.32
Fixed in: 3.1.32
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

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).

NVD CVE-2024-13482 WPScan advisory

medium 4.8 CVE-2024-13486 · published 2025-05-15

Stored cross-site scripting (XSS) in Icegram Engage (older than 3.1.32)

Affected: older than 3.1.32
Fixed in: 3.1.32
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

NVD CVE-2024-13486 WPScan advisory

medium 6.5 CVE-2025-24542 · published 2025-01-24

Stored cross-site scripting (XSS) in Icegram Engage (3.1.31 and older)

Affected: 3.1.31 and older
Fixed in: 3.1.32
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Icegram Icegram icegram allows Stored XSS.This issue affects Icegram: from n/a through <= 3.1.31.

NVD CVE-2025-24542 Patchstack advisory

medium 6.1 CVE-2024-12302 · published 2025-01-06

Stored cross-site scripting (XSS) in Icegram Engage (older than 3.1.32)

Affected: older than 3.1.32
Fixed in: 3.1.32
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

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

NVD CVE-2024-12302 WPScan advisory

medium 5.3 CVE-2024-39625 · published 2024-11-01

Missing authorization check in Icegram Engage (3.1.24 and older)

Affected: 3.1.24 and older
Fixed in: 3.1.25
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in icegram Icegram allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Icegram: from n/a through 3.1.24.

NVD CVE-2024-39625 Patchstack advisory

medium 5.3 CVE-2024-43272 · published 2024-08-19

Authentication bypass in Icegram Engage (3.1.24 and older)

Affected: 3.1.24 and older
Fixed in: 3.1.25
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authentication for Critical Function vulnerability in icegram Icegram allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Icegram: from n/a through 3.1.24.

NVD CVE-2024-43272 Patchstack advisory

medium 6.5 CVE-2024-43344 · published 2024-08-18

Stored cross-site scripting (XSS) in Icegram Engage (3.1.25 and older)

Affected: 3.1.25 and older
Fixed in: 3.1.26
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Icegram allows Stored XSS.This issue affects Icegram: from n/a through 3.1.25.

NVD CVE-2024-43344 Patchstack advisory

medium 5.4 CVE-2024-21748 · published 2024-06-08

Missing authorization check in Icegram Engage (3.1.21 and older)

Affected: 3.1.21 and older
Fixed in: 3.1.22
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Missing Authorization vulnerability in Icegram.This issue affects Icegram: from n/a through 3.1.21.

NVD CVE-2024-21748 Patchstack advisory

medium 5.4 CVE-2023-51532 · published 2024-02-01

Stored cross-site scripting (XSS) in Icegram Engage (3.1.19 and older)

Affected: 3.1.19 and older
Fixed in: 3.1.20
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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.

NVD CVE-2023-51532 Patchstack advisory

high 8.8 CVE-2023-52119 · published 2024-01-05

Cross-site request forgery (CSRF) in Icegram Engage (3.1.18 and older)

Affected: 3.1.18 and older
Fixed in: 3.1.19
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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.

NVD CVE-2023-52119 Patchstack advisory

medium 6.1 CVE-2023-2398 · published 2023-06-12

Reflected cross-site scripting (XSS) in Icegram Engage (older than 3.1.12)

Affected: older than 3.1.12
Fixed in: 3.1.12
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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

NVD CVE-2023-2398 WPScan advisory

medium 5.4 CVE-2021-36832 · published 2021-10-19

Cross-site scripting (XSS) in Icegram Engage (2.0.2 and older)

Affected: 2.0.2 and older
Fixed in: 2.0.3 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

WordPress Popups, Welcome Bar, Optins and Lead Generation Plugin – Icegram (versions <= 2.0.2) vulnerable at "Headline" (&message_data[16][headline]) input.

NVD CVE-2021-36832 Patchstack advisory wordpress.org

medium 6.5 CVE-2016-10962 · published 2019-09-16

Cross-site request forgery (CSRF) in Icegram Engage (older than 1.9.19)

Affected: older than 1.9.19
Fixed in: 1.9.19
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: advisory text · score by NVD

Details from the advisory

The icegram plugin before 1.9.19 for WordPress has CSRF via the wp-admin/edit.php option_name parameter.

NVD CVE-2016-10962 wordpress.org sumofpwn.nl

medium 6.1 CVE-2016-10963 · published 2019-09-16

Cross-site scripting (XSS) in Icegram Engage (older than 1.9.19)

Affected: older than 1.9.19
Fixed in: 1.9.19
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: advisory text · score by NVD

Details from the advisory

The icegram plugin before 1.9.19 for WordPress has XSS.

NVD CVE-2016-10963 wordpress.org

medium 5.4 CVE-2019-15830 · published 2019-08-30

Cross-site scripting (XSS) in Icegram Engage (older than 1.10.29)

Affected: older than 1.10.29
Fixed in: 1.10.29
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: advisory text · score by NVD

Details from the advisory

The icegram plugin before 1.10.29 for WordPress has ig_cat_list XSS.

NVD CVE-2019-15830 wordpress.org blog.sucuri.net wpvulndb.com

Recent activity

2026-10-30 — latest release on wordpress.org (3.1.47).
2026-10-01 — PHP object injection disclosed (CVE-2026-97284), fixed in 3.1.44.
2026-08-01 — SQL injection disclosed (CVE-2026-16087), fixed in 3.1.43.
2026-01-22 — Missing authorization check disclosed (CVE-2025-68507), fixed in 3.1.36.

Free. We check the CVE feeds every day and email you only when a new issue for Icegram Engage (icegram) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (10) · Missing authorization (3) · Cross-site request forgery (CSRF) (2) · PHP object injection (1) · SQL injection (1) · Authentication bypass (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/icegram (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/icegram"><img src="https://laskyr.com/plugins/icegram/badge.svg" alt="Icegram Engage vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Icegram Engage safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.1.47)

What to do

Check your version

Known vulnerabilities

PHP object injection in Icegram Engage (3.1.31 and older)

SQL injection in Icegram Engage (3.1.42 and older)

Missing authorization check in Icegram Engage (3.1.35 and older)

Stored cross-site scripting (XSS) in Icegram Engage (older than 3.1.32)

Stored cross-site scripting (XSS) in Icegram Engage (older than 3.1.32)

Stored cross-site scripting (XSS) in Icegram Engage (3.1.31 and older)

Stored cross-site scripting (XSS) in Icegram Engage (older than 3.1.32)

Missing authorization check in Icegram Engage (3.1.24 and older)

Authentication bypass in Icegram Engage (3.1.24 and older)

Stored cross-site scripting (XSS) in Icegram Engage (3.1.25 and older)

Missing authorization check in Icegram Engage (3.1.21 and older)

Stored cross-site scripting (XSS) in Icegram Engage (3.1.19 and older)

Cross-site request forgery (CSRF) in Icegram Engage (3.1.18 and older)

Reflected cross-site scripting (XSS) in Icegram Engage (older than 3.1.12)

Cross-site scripting (XSS) in Icegram Engage (2.0.2 and older)

Cross-site request forgery (CSRF) in Icegram Engage (older than 1.9.19)

Cross-site scripting (XSS) in Icegram Engage (older than 1.9.19)

Cross-site scripting (XSS) in Icegram Engage (older than 1.10.29)

Recent activity

Get an email when Icegram Engage has a new vulnerability

Browse vulnerabilities

Where this data comes from