CVE-2026-16087: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in icegram Icegram Engage – Popups, Optins, CTAs & Lead Generation
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.
AI Analysis
Technical Summary
The Icegram Engage plugin for WordPress suffers from a second-order SQL Injection vulnerability (CWE-89) in all versions up to 3.1.42. The issue occurs because the 'messages[][id]' parameter is insufficiently escaped and stored in post meta via the save_campaign_preview() AJAX action, which requires Editor-level or higher access. Later, when a preview request calls get_message_data(), the stored malicious id value is interpolated directly into a SQL IN() clause without using $wpdb->prepare() or integer casting, allowing an attacker to append additional SQL queries. This can lead to unauthorized extraction of sensitive information from the database. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, and limited privileges required.
Potential Impact
An authenticated attacker with contributor-level or higher privileges can exploit this vulnerability to perform second-order SQL Injection attacks. This can result in unauthorized disclosure of sensitive database information. The vulnerability does not impact integrity or availability directly but compromises confidentiality by allowing data extraction through crafted SQL queries.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict contributor-level and higher access to trusted users only. Monitor for updates from the vendor regarding patches or official fixes. Avoid using affected versions in sensitive environments if possible.
CVE-2026-16087: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in icegram Icegram Engage – Popups, Optins, CTAs & Lead Generation
Description
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.
CVSS v3.1
Score 6.5medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Icegram Engage plugin for WordPress suffers from a second-order SQL Injection vulnerability (CWE-89) in all versions up to 3.1.42. The issue occurs because the 'messages[][id]' parameter is insufficiently escaped and stored in post meta via the save_campaign_preview() AJAX action, which requires Editor-level or higher access. Later, when a preview request calls get_message_data(), the stored malicious id value is interpolated directly into a SQL IN() clause without using $wpdb->prepare() or integer casting, allowing an attacker to append additional SQL queries. This can lead to unauthorized extraction of sensitive information from the database. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, and limited privileges required.
Potential Impact
An authenticated attacker with contributor-level or higher privileges can exploit this vulnerability to perform second-order SQL Injection attacks. This can result in unauthorized disclosure of sensitive database information. The vulnerability does not impact integrity or availability directly but compromises confidentiality by allowing data extraction through crafted SQL queries.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict contributor-level and higher access to trusted users only. Monitor for updates from the vendor regarding patches or official fixes. Avoid using affected versions in sensitive environments if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-17T13:53:29.064Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6daf5bbf32cb7a346ced87
Added to database: 08/01/2026, 08:33:31 UTC
Last enriched: 08/01/2026, 08:51:33 UTC
Last updated: 08/01/2026, 21:27:16 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.