# CVE-2026-16087: Icegram Engage second-order SQL injection in messages parameter

Source: https://junglewise.ai/threats/cve-2026-16087-icegram-engage-second-order-sql-injection-in-messages-parameter  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-01. Updated: 2026-08-01  
License: CC BY 4.0 with a link back

CVE-2026-16087 · Severity: medium · CVSS 6.5 · Published 2026-08-01

Icegram Engage, a WordPress plugin used for creating popups and lead generation forms, contains a security flaw that could allow an attacker to steal sensitive information from a website's database. By exploiting this vulnerability, a user with basic contributor-level access can inject malicious commands that are later executed by the system. This could lead to the unauthorized disclosure of customer data or internal site configuration details.

Vendors: [Icegram](https://junglewise.ai/threats/vendors/icegram).

## Quick answers

**Is CVE-2026-16087 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-16087 being exploited in the wild.

**How severe is CVE-2026-16087?** Medium severity, with a CVSS score of 6.5, published 1 August 2026.

**Which products and versions are affected?** Icegram Engage up to, and including, 3.1.42.

**Is there a fix for CVE-2026-16087?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-16087 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-16087?** Check whether you run Icegram Engage at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The Icegram Engage plugin for WordPress is vulnerable to second-order SQL Injection due to insufficient escaping and lack of preparation in SQL queries within the get_message_data() function. The vulnerability is triggered when a malicious 'id' value is persisted to post meta via the save_campaign_preview() AJAX action. This stored value is subsequently interpolated directly into a SQL IN() clause without using $wpdb->prepare() or integer casting during a preview request. Authenticated attackers with contributor-level access or higher can exploit this to append additional SQL queries and extract sensitive data from the database. The issue is addressed in version 3.1.43.

## Affected products

- Icegram Icegram Engage – Popups, Optins, CTAs & Lead Generation up to, and including, 3.1.42

## Timeline

- 2026-08-01: disclosed
- 2026-08-01: advisory

## References

- [https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/class-icegram.php](https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/class-icegram.php)
- [https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/class-icegram.php](https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/class-icegram.php)
- [https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/class-icegram.php](https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/class-icegram.php)
- [https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/classes/class-icegram-campaign-admin.php](https://plugins.trac.wordpress.org/browser/icegram/tags/3.1.42/lite/classes/class-icegram-campaign-admin.php)
- [https://plugins.trac.wordpress.org/changeset?reponame=&old=3628434%40icegram&new=3628434%40icegram](https://plugins.trac.wordpress.org/changeset?reponame=&old=3628434%40icegram&new=3628434%40icegram)
- [https://www.wordfence.com/threat-intel/vulnerabilities/id/1543265e-dbbf-4d48-aaa9-353e2a5c3fe9?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/1543265e-dbbf-4d48-aaa9-353e2a5c3fe9?source=cve)