Stored XSS via unescaped inline-script JSON
Published Jul 14, 2026 · Updated Jul 14, 2026
Stored XSS in Hi.Events before 1.11.0 allows remote authenticated users to execute JavaScript in event-page visitors' browsers. The event title is serialized with JSON.stringify into application/ld+json and rehydrated-state script blocks without escaping a closing script sequence. Event creation or edit permission is required, and execution occurs when an unauthenticated visitor or authenticated administrator opens the public event page.
Summary
What happened
Stored XSS in Hi.Events before 1.11.0 allows remote authenticated users to execute JavaScript in event-page visitors' browsers. The event title is serialized with JSON.stringify into application/ld+json and rehydrated-state script blocks without escaping a closing script sequence. Event creation or edit permission is required, and execution occurs when an unauthenticated visitor or authenticated administrator opens the public event page.
The record
- CVE
- CVE-2026-60119
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Hi.Events
- Product
- Hi.Events
- Classifications
- CWE-862, CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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.11.0
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
- GHSA-2ggx-79g6-2jmj proof of conceptproof of concept · demonstrated
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