CVE-2026-16087: Icegram Engage <= 3.1.42 - Authenticated (Contributor+) Second-Order SQL Injection via 'messages[][id]' Parameter
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 savecampaignpreview() AJAX action (gated by a nonce check and editpost capability, requiring Editor-level access or above), and only executed as SQL when a subsequent preview request triggers getmessagedata() to interpolate the stored value directly into a SQL IN() clause without $wpdb->prepare() or integer casting.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-16087?
The severity of CVE-2026-16087 is rated medium with a CVSS score of 6.5.
How do I fix CVE-2026-16087?
To fix CVE-2026-16087, update the Icegram Engage plugin to version 3.1.43 or later.
What type of vulnerability is CVE-2026-16087?
CVE-2026-16087 is a second-order SQL Injection vulnerability.
Who is affected by CVE-2026-16087?
CVE-2026-16087 affects all versions of the Icegram Engage plugin for WordPress up to and including 3.1.42.
What causes CVE-2026-16087?
CVE-2026-16087 is caused by insufficient escaping on user supplied parameters in the 'messages[][id]' parameter.