CVE-2026-16087
Received Received - Intake

SQL Injection in Icegram Engage WordPress Plugin

Publication date: 2026-08-01

Last updated on: 2026-08-01

Assigner: Wordfence

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-01
Last Modified
2026-08-01
Generated
2026-08-01
AI Q&A
2026-08-01
EPSS Evaluated
N/A
NVD
CVE-2026-16087
EUVD
EUVD-2026-51742

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
icegram engage to 3.1.42 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a second-order SQL Injection in the Icegram Engage WordPress plugin up to version 3.1.42. It occurs due to insufficient escaping of the 'messages[][id]' parameter and lack of proper SQL query preparation. Authenticated attackers with contributor-level access or higher can inject malicious SQL queries that extract sensitive database information.

Detection Guidance

This vulnerability requires WordPress with the Icegram Engage plugin (versions up to 3.1.42) installed. Detection involves checking plugin versions and reviewing database queries for suspicious patterns. No specific commands are provided in the context.

Impact Analysis

If exploited, this vulnerability could allow attackers to extract sensitive data from your WordPress database, such as user credentials, personal information, or other confidential data. Attackers need at least contributor-level access to exploit it.

Compliance Impact

This vulnerability could lead to unauthorized data access, potentially violating GDPR (data protection) and HIPAA (health information privacy) by exposing sensitive user data. Organizations using this plugin may face compliance violations and legal consequences if exploited.

Mitigation Strategies

Update the Icegram Engage plugin to the latest version beyond 3.1.42. Remove contributor-level or higher access for untrusted users. Review database logs for unusual SQL queries. Disable plugin functionality if not essential.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-16087. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart