Stored script execution via unescaped page content
Published Jan 24, 2025 · Updated May 12, 2026
Stored cross-site scripting in Icegram Engage 3.1.31 and earlier allows remote authenticated users to inject scripts into pages. No public source identifies the affected field or function; published analysis attributes the flaw to insufficient sanitization of stored content and missing output escaping. Contributor-level access is required, and the script executes in another user's browser when that user opens an injected page.
Summary
What happened
Stored cross-site scripting in Icegram Engage 3.1.31 and earlier allows remote authenticated users to inject scripts into pages. No public source identifies the affected field or function; published analysis attributes the flaw to insufficient sanitization of stored content and missing output escaping. Contributor-level access is required, and the script executes in another user's browser when that user opens an injected page.
The record
- CVE
- CVE-2025-24542
- Published
- Jan 24, 2025
- Updated
- May 12, 2026
- Vendor
- Icegram
- Product
- Icegram Engage
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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.31 changes=[{"at":"3.1.32","status":"unaffected"}]
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