Authenticated database disclosure via stored message-ID SQL injection
Published Aug 1, 2026 · Updated Aug 1, 2026
SQL injection in Icegram Engage 3.1.42 and earlier allows remote authenticated users to read database data through a stored message ID. The save_campaign_preview() AJAX action stores the messages[][id] value in post meta, and get_message_data() later inserts it into a SQL IN() clause without preparation or integer casting. Reaching the storage step requires a valid nonce and edit_post capability, which limits the demonstrated path to Editor-level access or above.
Summary
What happened
SQL injection in Icegram Engage 3.1.42 and earlier allows remote authenticated users to read database data through a stored message ID. The save_campaign_preview() AJAX action stores the messages[][id] value in post meta, and get_message_data() later inserts it into a SQL IN() clause without preparation or integer casting. Reaching the storage step requires a valid nonce and edit_post capability, which limits the demonstrated path to Editor-level access or above.
The record
- CVE
- CVE-2026-16087
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Icegram
- Product
- Icegram Engage
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.1.42
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo