Is CVE-2026-60119 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-60119 being exploited in the wild.

How severe is CVE-2026-60119?

Medium severity, with a CVSS score of 5.4, published 14 July 2026.

Which products and versions are affected?

HiEventsDev Hi.Events <= v1.10.0-beta.

Is there a fix for CVE-2026-60119?

A patch was published on 2026-07-07: Fix committed to main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-60119 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-60119?

Check whether you run HiEventsDev Hi.Events at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-60119: HiEvents Hi.Events stored XSS via event title in inline scripts

Q: Is there a fix for CVE-2026-60119?

A patch was published on 2026-07-07: Fix committed to main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-60119 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-60119?

Check whether you run HiEventsDev Hi.Events at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-60119 · Severity: medium · CVSS 5.4 · Published 2026-07-14

Hi.Events is an open-source event management and ticketing platform. A security vulnerability allows users with event creation or editing permissions to inject malicious scripts into event titles. When other users, including administrators or public visitors, view the affected event page, the malicious script executes in their browser. This could lead to unauthorized actions being performed on behalf of the victim or the theft of sensitive session information.

Technologies: HiEventsDev Hi.Events. Vendors: HiEventsDev.

Quick answers

Is CVE-2026-60119 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-60119 being exploited in the wild.
How severe is CVE-2026-60119?: Medium severity, with a CVSS score of 5.4, published 14 July 2026.
Which products and versions are affected?: HiEventsDev Hi.Events <= v1.10.0-beta.
Is there a fix for CVE-2026-60119?: A patch was published on 2026-07-07: Fix committed to main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-60119 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-60119?: Check whether you run HiEventsDev Hi.Events at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A stored cross-site scripting (XSS) vulnerability exists in Hi.Events through version 1.10.0-beta. The vulnerability occurs because the event title field is serialized using JSON.stringify() and embedded directly into inline <script> tags within the application/ld+json structured data block and the server-side rehydrated state. Since JSON.stringify() does not escape the '</script>' sequence by default, an attacker with event creation or edit permissions can provide a title containing this sequence to break out of the script context and inject arbitrary HTML or JavaScript. The payload executes in the context of any user viewing the event page, including unauthenticated visitors and administrators. The issue is fixed in version 1.11.0-beta by properly escaping user-controlled data before embedding it in inline script contexts and stripping control characters.

Affected products

HiEventsDev Hi.Events <= v1.10.0-beta

Timeline

2026-07-07: patched: Fix committed to main branch
2026-07-09: patched: Version 1.11.0-beta released
2026-07-13: advisory: GitHub Security Advisory published
2026-07-14: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.