Stored XSS via unescaped ticket names
Published Oct 24, 2024 · Updated Apr 8, 2026
Stored XSS in EventPrime 4.0.4.7 and earlier allows remote attackers to inject scripts through ticket names in front-end events. The front-end event-submission path stores ticket-name input without sufficient sanitization, and affected views render it without context-appropriate escaping. Exploitation requires front-end event submission with tickets to be enabled and a user to open the injected page, where the script runs in that user's browser.
Summary
What happened
Stored XSS in EventPrime 4.0.4.7 and earlier allows remote attackers to inject scripts through ticket names in front-end events. The front-end event-submission path stores ticket-name input without sufficient sanitization, and affected views render it without context-appropriate escaping. Exploitation requires front-end event submission with tickets to be enabled and a user to open the injected page, where the script runs in that user's browser.
The record
- CVE
- CVE-2024-9864
- Published
- Oct 24, 2024
- Updated
- Apr 8, 2026
- Vendor
- EventPrime Events
- Product
- EventPrime
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 24, 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 <=4.0.4.7
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