CVE-2026-60119

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. 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: epss, secondary
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jul 16, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
github Patch Available🟡 PoC Available

Stored XSS via Event Title on Public Event Page · Advisory · HiEventsDev/Hi.Events · GitHub

https://github.com/HiEventsDev/Hi.Events/security/advisories/GHSA-2ggx-79g6-2jmj
generic

Hi.Events < 1.11.0 XSS via Event Title JSON.stringify Injection | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hi-events-beta-xss-via-event-title-json-stringify-injection
github_release Patch Available

v.1.11.0-beta

Patch available: HiEventsDev/Hi.Events v.1.11.0-beta

https://github.com/HiEventsDev/Hi.Events/releases/tag/v.1.11.0-beta
github_pr Patch Available

fix: prevent XSS via event title in inline script contexts

Patch available: HiEventsDev/Hi.Events v.1.11.0-beta (PR #1260 merged 2026-07-07)

https://github.com/HiEventsDev/Hi.Events/pull/1260
github_commit Patch Available

commit 1e36b0707718 (HiEventsDev/Hi.Events)

Patch available: HiEventsDev/Hi.Events v.1.11.0-beta (contains commit 1e36b0707718)

https://github.com/HiEventsDev/Hi.Events/commit/1e36b070771801ed7113255ef7b3a7f271a2a794

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 38× 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.

  1. 2026-08-03 12:07 UTCEG score recompute
  2. 2026-08-03 10:36 UTCEPSS rescore
  3. 2026-08-02 11:39 UTCEG score recompute
  4. 2026-08-02 02:27 UTCEPSS rescore
  5. 2026-08-01 11:46 UTCEG score recompute
  6. 2026-08-01 04:16 UTCEPSS rescore
  7. 2026-07-31 11:55 UTCEG score recompute
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 12:04 UTCEG score recompute
  10. 2026-07-30 01:30 UTCEPSS rescore
  11. 2026-07-30 01:30 UTCEPSS rescore
  12. 2026-07-29 12:00 UTCEG score recompute
  13. 2026-07-28 15:37 UTCEPSS rescore
  14. 2026-07-28 12:08 UTCEG score recompute
  15. 2026-07-27 14:14 UTCEPSS rescore
  16. 2026-07-27 11:36 UTCEG score recompute
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 14:54 UTCEPSS rescore
  19. 2026-07-26 11:45 UTCEG score recompute
  20. 2026-07-25 14:18 UTCEPSS rescore
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-24 14:18 UTCEPSS rescore
  23. 2026-07-24 14:18 UTCEPSS rescore
  24. 2026-07-23 14:18 UTCEPSS rescore
  25. 2026-07-23 14:18 UTCEPSS rescore
Show 13 more
  1. 2026-07-23 03:21 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-14 16:10 UTCEG score recompute
  13. 2026-07-14 16:10 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
What is the CVSS score of CVE-2026-60119?
CVE-2026-60119 has a CVSS v3 base score of 5.4 (NVD).
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

Explore →

Is Your Infrastructure Affected by CVE-2026-60119?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs