{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-16087 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-16087 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-16087 is a medium-severity SQL injection vulnerability in Icegram Engage – Popups, Optins, CTAs \u0026 Lead Generation, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-16087 and fix it if it is affected.\n\nWhat it is: CVE-2026-16087 is a medium-severity SQL injection vulnerability in Icegram Engage – Popups, Optins, CTAs \u0026 Lead Generation, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-16087 in the wild and no public exploit code.\n\nAffected product: Icegram Engage – Popups, Optins, CTAs \u0026 Lead Generation. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-16087/ (Markdown: https://insights.sbomify.com/CVE-2026-16087/index.md)","id":"CVE-2026-16087","markdown":"https://insights.sbomify.com/CVE-2026-16087/index.md","name":"CVE-2026-16087","record":{"aliases":["GHSA-353r-r23c-w3ph"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers with contributor access can exploit second-order SQL injection to extract sensitive database information from the Icegram Engage plugin.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The Icegram Engage – Popups, Optins, CTAs \u0026 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-\u003eprepare() or integer casting.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Icegram Engage \u003c= 3.1.42 - Authenticated (Contributor+) Second-Order SQL Injection via 'messages[][id]' Parameter","id":"CVE-2026-16087","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"halo-dev halo Files Backup Endpoint MigrationEndpoint.java download path traversal","id":"CVE-2026-16088"},"packages":[],"prev":{"headline":"Sipeed PicoClaw context.go NewContextBuilder inclusion of functionality from untrusted control sphere","id":"CVE-2026-16085"},"products":["Icegram Engage – Popups, Optins, CTAs \u0026 Lead Generation"],"published":"2026-08-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["icegram"]},"summary":"Authenticated attackers with contributor access can exploit second-order SQL injection to extract sensitive database information from the Icegram Engage plugin.","url":"https://insights.sbomify.com/CVE-2026-16087/"}