Unauthenticated stored XSS via unescaped feedback names
Published Jul 12, 2024 · Updated Apr 8, 2026
Stored XSS in Awesome Motive UserFeedback 1.0.15 and earlier allows remote attackers to inject scripts through feedback names. The frontend feedback handler stores the name parameter without sufficient sanitization, and the privileged response view renders it without sufficient output escaping. No account is required to submit the payload, but script execution occurs when a high-privileged user views the stored response.
Summary
What happened
Stored XSS in Awesome Motive UserFeedback 1.0.15 and earlier allows remote attackers to inject scripts through feedback names. The frontend feedback handler stores the name parameter without sufficient sanitization, and the privileged response view renders it without sufficient output escaping. No account is required to submit the payload, but script execution occurs when a high-privileged user views the stored response.
The record
- CVE
- CVE-2024-5902
- Published
- Jul 12, 2024
- Updated
- Apr 8, 2026
- Vendor
- Awesome Motive
- Product
- UserFeedback
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 12, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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 <=1.0.15
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