CVE-2024-13482: The Icegram Engage WordPress plugin before 3.1.32 does not sanitise and escape some of its settings, which co

Q: How do I fix CVE-2024-13482?

icegram engage: upgrade to 3.1.32. Exact commands for each OS are on this page.

Q: Is CVE-2024-13482 being exploited?

CVE-2024-13482 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-13482 affect?

CVE-2024-13482 affects icegram engage. Severity is medium (CVSS 4.8). The Icegram Engage WordPress plugin before 3.1.32 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capabili

Q: How urgent is CVE-2024-13482?

Priority 28/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2024-13482 is a medium-severity flaw (CVSS 4.8) affecting icegram engage. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Icegram Engage WordPress plugin before 3.1.32 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-05-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: icegram

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-15 20:15 UTCPublished CVE record published
2026-06-17 07:02 UTCUpdated Record last modified

icegram icegram engage UPGRADE

Affected: < 3.1.32

Fixed in: 3.1.32

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy icegram-engage || rpm -q icegram-engage || icegram-engage --version

2. UPGRADE to 3.1.32 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade icegram-engage

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade icegram-engage

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-13482?

icegram engage: upgrade to 3.1.32. Exact commands for each OS are on this page.

Is CVE-2024-13482 being exploited?

CVE-2024-13482 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-13482 affect?

CVE-2024-13482 affects icegram engage. Severity is medium (CVSS 4.8). The Icegram Engage WordPress plugin before 3.1.32 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capabili

How urgent is CVE-2024-13482?

Priority 28/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-13486 MEDIUM 4.8 UPGRADE The Icegram Engage WordPress plugin before 3.1.32 does not sanitise and escape some of its settings, which co
CVE-2024-12302 MEDIUM 6.1 UPGRADE The Icegram Engage WordPress plugin before 3.1.32 does not sanitise and escape some of its Campaign settings,
CVE-2023-51532 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Icegram

References

← Back to latest CVEs