dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-60119

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Hi.Events before 1.11.0 allows authenticated users with event creation/edit permissions to inject XSS via malicious event titles containing the </script> sequence. The vulnerability exists because event titles are not properly escaped when embedded in inline script tags using JSON.stringify(), allowing attackers to break out of the script context in application/ld+json structured data or server-side rehydrated state. This stored XSS executes in browsers of anyone viewing the public event page, including unauthenticated visitors and administrators.

MitigationUpgrade to Hi.Events version 1.11.0 or later, which should include proper escaping of event titles in inline script contexts; alternatively, implement context-aware output encoding for event titles in JSON.stringify() embedded scripts and ensure application/ld+json data properly escapes special characters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hi.Events installation
    Locate the Hi.Events application in your environment. Check for the main application directory or container image. Look for files such as package.json, composer.json, or the main application entry point.
    Affected if Hi.Events is present in your environment
  2. Determine installed Hi.Events version
    Check the version file or application metadata. Common locations: package.json (Node.js), composer.json (PHP), version.php, or the admin dashboard if accessible. Compare the version number to the affected range (before 1.11.0).
    Affected if The installed version is 1.10.x or earlier, or any version below 1.11.0
  3. Verify event creation or editing capability exists
    Confirm that the application has event management functionality enabled. This may involve checking user roles, permissions configuration, or the presence of event creation forms in the application's route structure.
    Affected if Authenticated users can create new events or edit existing events in the system
  4. Confirm public event pages are accessible
    Verify that the application exposes public-facing event pages. Check the application's routing configuration or attempt to access a public event URL pattern (commonly /event/{slug} or /events/{id}).
    Affected if Public event pages are accessible to unauthenticated visitors, allowing stored XSS to execute in their browsers

Your environment is affected if Hi.Events version is below 1.11.0 and the application permits authenticated users to create or edit events, as the injected script will execute on public event pages viewed by anyone.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Hi.Events version 1.11.0 or later, which should include proper escaping of event titles in inline script contexts; alternatively, implement context-aware output encoding for event titles in JSON.stringify() embedded scripts and ensure application/ld+json data properly escapes special characters.

Recommended fix High confidence

Hi.Events 1.11.0 or later

  1. Upgrade Hi.Events to version 1.11.0 or later to resolve the XSS vulnerability
  2. After upgrading, verify that event titles are properly escaped when rendered in inline script tags and application/ld+json structured data
  3. Review existing events for any malicious titles containing </script> or similar injection attempts
  4. Ensure proper input validation and output encoding is maintained for all user-generated content

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60119 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data