Hi.Events before 1.11.0 contains a cross-site scripting vulnerability that allows authenticated attackers with event creation or edit permissions to inject arbitrary HTML and JavaScript by embedding a malicious event title containing the sequence, which is not escaped by JSON.stringify() when embedded in inline script tags. Attackers can craft an event title that breaks out of the script context in the application/ld+json structured data block or server-side rehydrated state, causing the payload to execute in the browser of any user who views the public event page, including unauthenticated visitors and authenticated administrators.
CVE-2026-60119
MEDIUMPre-NVD 5.45.4Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(low)
- EPSS
- 6.7%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
References (6)
- disclosure@vulncheckhttps://github.com/HiEventsDev/Hi.Events/commit/1e36b070771801ed7113255ef7b3a7f271a2a794
- disclosure@vulncheckhttps://github.com/HiEventsDev/Hi.Events/pull/1260
- disclosure@vulncheckhttps://github.com/HiEventsDev/Hi.Events/releases/tag/v.1.11.0-beta
- disclosure@vulncheckhttps://github.com/HiEventsDev/Hi.Events/security/advisories/GHSA-2ggx-79g6-2jmj
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/hi-events-beta-xss-via-event-title-json-stringify-injection
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/HiEventsDev/Hi.Events/security/advisories/GHSA-2ggx-79g6-2jmj
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:01 UTCEG score recompute
- 2026-07-14 16:10 UTCEG score recompute
- 2026-07-14 16:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(5)
What is CVE-2026-60119?
CVE-2026-60119 is a medium vulnerability published on July 14, 2026. Hi.Events before 1.11.0 contains a cross-site scripting vulnerability that allows authenticated attackers with event creation or edit permissions to inject arbitrary HTML and JavaScript by embedding a malicious event title containing the </script> sequence, which is not escaped by JSON.stringify()…
When was CVE-2026-60119 disclosed?
CVE-2026-60119 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60119 actively exploited?
CVE-2026-60119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-60119?
CVE-2026-60119 has a CVSS v3 base score of 5.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-60119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60119, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-60119
Is Your Infrastructure Affected by CVE-2026-60119?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.