Reflected XSS via unescaped message identifier
Published Dec 21, 2021 · Updated Aug 3, 2024
Reflected XSS in Icegram Engage before 2.0.5 allows remote attackers to execute script in a visitor's browser via a crafted request. The get_message_action_row AJAX handler places the unsanitized, unescaped message_id parameter into an HTML attribute, allowing attribute-context script injection. Exploitation requires a user to open the crafted request; injected script runs in the affected site's origin and can read or alter browser-accessible page data.
Summary
What happened
Reflected XSS in Icegram Engage before 2.0.5 allows remote attackers to execute script in a visitor's browser via a crafted request. The get_message_action_row AJAX handler places the unsanitized, unescaped message_id parameter into an HTML attribute, allowing attribute-context script injection. Exploitation requires a user to open the crafted request; injected script runs in the affected site's origin and can read or alter browser-accessible page data.
The record
- CVE
- CVE-2021-24941
- Published
- Dec 21, 2021
- Updated
- Aug 3, 2024
- Vendor
- Icegram
- Product
- Icegram Engage
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=2.0.5 <2.0.5
What conditions does exploitation require?
What is affected?
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