CVE-2025-24542
📋 TL;DR
This stored cross-site scripting (XSS) vulnerability in the Icegram Engage WordPress plugin allows attackers to inject malicious scripts into web pages that are then executed when other users view those pages. All WordPress sites using Icegram Engage versions up to 3.1.31 are affected. Attackers can steal session cookies, redirect users, or perform actions on their behalf.
💻 Affected Systems
- Icegram Engage WordPress Plugin
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Attackers could steal administrator session cookies, take over WordPress sites, install backdoors, deface websites, or redirect visitors to malicious sites.
Likely Case
Attackers inject malicious JavaScript to steal user session cookies, potentially compromising user accounts and performing unauthorized actions.
If Mitigated
With proper input validation and output encoding, malicious scripts would be neutralized before reaching users, preventing exploitation.
🎯 Exploit Status
XSS vulnerabilities are commonly exploited and weaponized. The Patchstack reference provides technical details that could be used to create exploits.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 3.1.32 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Icegram Engage and click 'Update Now'. 4. Verify version is 3.1.32 or higher.
🔧 Temporary Workarounds
Disable Icegram Plugin
allTemporarily disable the vulnerable plugin until patched
wp plugin deactivate icegram
Implement WAF Rules
allAdd web application firewall rules to block XSS payloads targeting Icegram endpoints
🧯 If You Can't Patch
- Implement Content Security Policy (CSP) headers to restrict script execution
- Use WordPress security plugins with XSS protection features
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel → Plugins → Icegram Engage → Version number. If version is 3.1.31 or lower, you are vulnerable.Check Version:
wp plugin get icegram --field=versionVerify Fix Applied:
After updating, verify version shows 3.1.32 or higher in WordPress plugins list.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to Icegram endpoints
- JavaScript payloads in request parameters
- Multiple failed XSS attempts
Network Indicators:
- Malicious script tags in HTTP requests to /wp-content/plugins/icegram/
- Unusual traffic patterns to Icegram admin endpoints
SIEM Query:
source="web_server" AND (uri_path="/wp-content/plugins/icegram/" OR user_agent CONTAINS "<script>")