WordPress plugin · Updated daily · Source: Wordfence Intelligence

Icegram Engage vulnerabilities: affected versions and fixes

Icegram Engage has 10,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Icegram Engage at a glance

  • 19 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Oct 1, 2026.
  • Ranked #1472 by popularity on WordPress.org (10,000+ active installs).
  • The latest version is 3.1.50 (released Nov 18, 2026). The most recent security fix shipped in 3.1.44.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Icegram Engage version

Enter the Icegram Engage version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Icegram Engage”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Icegram Engage”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (3.1.50). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Icegram Engage vulnerabilities

  • Icegram Engage – Popups, Optins, CTAs & Lead Generation <= 3.1.31 - Authenticated (Contributor+) PHP Object Injection

    PHP object injection · CVE-2026-97284

    Affected versions: ≤ 3.1.31

    Fixed in: 3.1.44

    Severity: High 7.5 · Disclosed Oct 1, 2026

  • Icegram Engage <= 3.1.42 - Authenticated (Contributor+) Second-Order SQL Injection via 'messages[][id]' Parameter

    SQL injection · CVE-2026-16087

    Affected versions: ≤ 3.1.42

    Fixed in: 3.1.43

    Severity: Medium 6.5 · Disclosed Jul 31, 2026

  • Icegram <= 3.1.35 - Missing Authorization

    Missing authorization · CVE-2025-68507

    Affected versions: ≤ 3.1.35

    Fixed in: 3.1.36

    Severity: Medium 5.3 · Disclosed Jan 5, 2026

  • Icegram Engage <= 3.1.31 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-13482

    Affected versions: ≤ 3.1.31

    Fixed in: 3.1.32

    Severity: Medium 4.4 · Disclosed Mar 3, 2025

  • Icegram <= 3.1.31 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-24542

    Affected versions: ≤ 3.1.31

    Fixed in: 3.1.32

    Severity: Medium 6.4 · Disclosed Jan 24, 2025

  • Icegram Engage <= 3.1.31 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-12302

    Affected versions: ≤ 3.1.31

    Fixed in: 3.1.32

    Severity: Medium 6.4 · Disclosed Dec 16, 2024

  • Icegram <= 3.1.25 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-43344

    Affected versions: ≤ 3.1.25

    Fixed in: 3.1.26

    Severity: Medium 6.4 · Disclosed Aug 16, 2024

  • Icegram <= 3.1.24 - Missing Authorization

    Missing authorization · CVE-2024-43272

    Affected versions: ≤ 3.1.24

    Fixed in: 3.1.25

    Severity: Medium 5.3 · Disclosed Aug 12, 2024

  • Icegram <= 3.1.24 - Missing Authorization to Unauthenticated Message Duplication

    Missing authorization · CVE-2024-39625

    Affected versions: ≤ 3.1.24

    Fixed in: 3.1.25

    Severity: Medium 5.3 · Disclosed Jul 22, 2024

  • Icegram <= 3.1.21 - Missing Authorization

    Missing authorization · CVE-2024-21748

    Affected versions: ≤ 3.1.21

    Fixed in: 3.1.22

    Severity: Medium 4.3 · Disclosed Jan 5, 2024

  • Icegram <= 3.1.18 - Cross-Site Request Forgery via save_campaign_preview

    Cross-site request forgery (CSRF) · CVE-2023-52119

    Affected versions: ≤ 3.1.18

    Fixed in: 3.1.19

    Severity: Medium 4.3 · Disclosed Dec 28, 2023

  • Icegram <= 3.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via Campaign Message

    Cross-site scripting (XSS) · CVE-2023-51532

    Affected versions: ≤ 3.1.19

    Fixed in: 3.1.20

    Severity: Medium 6.4 · Disclosed Dec 27, 2023

  • Icegram Engage <= 3.1.11 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-2398

    Affected versions: ≤ 3.1.11

    Fixed in: 3.1.12

    Severity: Medium 6.1 · Disclosed May 22, 2023

  • Icegram Engage <= 2.1.7 - Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-1776

    Affected versions: < 2.1.8

    Fixed in: 2.1.8

    Severity: Medium 6.1 · Disclosed May 30, 2022

  • Icegram <= 2.0.4 - Reflected Cross-Site Scripting via message_id

    Cross-site scripting (XSS) · CVE-2021-24941

    Affected versions: < 2.0.5

    Fixed in: 2.0.5

    Severity: Medium 6.1 · Disclosed Nov 22, 2021

  • Icegram <= 2.0.2 - Authenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-36832

    Affected versions: ≤ 2.0.2

    Fixed in: 2.0.3

    Severity: Medium 4.8 · Disclosed Aug 17, 2021

  • Icegram <= 1.10.28.2 - Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2019-15830

    Affected versions: ≤ 1.10.28.2

    Fixed in: 1.10.29

    Severity: Medium 6.4 · Disclosed Jul 9, 2019

  • Icegram <= 1.9.18 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2016-10962

    Affected versions: < 1.9.19

    Fixed in: 1.9.19

    Severity: High 8.8 · Disclosed Jul 19, 2016

  • Icegram <= 1.9.18 - Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2016-10963

    Affected versions: < 1.9.19

    Fixed in: 1.9.19

    Severity: Medium 6.1 · Disclosed Jul 19, 2016

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 1, 2026.

Most common weaknesses in Icegram Engage

Cross-site scripting (XSS)

11 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

4 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Cross-site request forgery (CSRF)

2 issues

If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.

Frequently asked questions

Is Icegram Engage safe to use?

Icegram Engage is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.1.50) and turn on automatic updates.

How do I find which version of Icegram Engage my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesIcegram Engage on WordPress.org