# CVE-2026-60119: Hi.Events < 1.11.0 XSS via Event Title JSON.stringify Injection

> Authenticated attackers can inject malicious scripts via event titles, leading to code execution and potential account takeover for users viewing public event pages.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-2ggx-79g6-2jmj

## What is CVE-2026-60119?

CVE-2026-60119 is a medium-severity cross-site scripting vulnerability in HiEventsDev Hi.Events, published on 14 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-60119?


## How do I fix CVE-2026-60119?

No fix has been published for CVE-2026-60119 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-60119 being exploited?

There is no known exploitation of CVE-2026-60119 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60119 and fix it if it is affected.

What it is: CVE-2026-60119 is a medium-severity cross-site scripting vulnerability in HiEventsDev Hi.Events, published on 14 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-60119 in the wild and no public exploit code.

Affected product: HiEventsDev Hi.Events. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60119/ (Markdown: https://insights.sbomify.com/CVE-2026-60119/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60119
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60119
- OSV: https://osv.dev/vulnerability/CVE-2026-60119

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60119/
Summaries are generated and may contain mistakes; the official description above is the record.