dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-60118

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 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 missing server-side visibility enforcement vulnerability that allows unauthenticated attackers to purchase hidden tickets by referencing hidden product and price IDs in order creation requests without authorization checks. Attackers can enumerate sequential hidden ticket IDs from visible ones and submit order creation requests referencing those IDs to purchase VIP, invite-only, or discounted tickets intentionally withheld from public sale.

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 · high confidence

Hi.Events before 1.11.0 lacks server-side authorization checks when creating orders, allowing unauthenticated attackers to purchase hidden tickets by directly referencing hidden product/price IDs in order creation API requests. Attackers can enumerate sequential ticket IDs to discover and purchase VIP, invite-only, or discounted tickets intentionally withheld from public sale.

MitigationImplement server-side authorization and visibility validation in the order creation endpoint to verify the requester is authorized to purchase a specific ticket and that the ticket is publicly visible before processing any order.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 and version
    Check the installed version of Hi.Events (e.g., check package.json, docker image tag, or application footer/admin panel for version number)
    Affected if The installed version is before 1.11.0
  2. Confirm order creation API endpoint is accessible
    Test if the order creation endpoint (typically POST /api/orders or /api/bookings) responds to unauthenticated requests
    Affected if The endpoint accepts requests without authentication tokens or session cookies
  3. Verify hidden ticket products exist
    Query the database or admin panel to list ticket products and check if any have visibility set to hidden, private, or unpublished
    Affected if Hidden or non-publicly-visible ticket products exist in the system
  4. Test direct ID access for hidden tickets
    Attempt to create an order by directly referencing a hidden ticket ID in API requests without prior enumeration
    Affected if Orders can be created using hidden ticket IDs without receiving authorization or visibility validation errors
  5. Check for sequential ID enumeration
    Submit multiple order creation requests with incrementally sequenced ticket IDs to discover hidden products
    Affected if Hidden tickets are discoverable through sequential ID probing

If Hi.Events before 1.11.0 is running and the order creation endpoint accepts unauthenticated requests, the environment is affected by this vulnerability.

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

Implement server-side authorization and visibility validation in the order creation endpoint to verify the requester is authorized to purchase a specific ticket and that the ticket is publicly visible before processing any order.

Recommended fix Moderate confidence

Hi.Events version 1.11.0

  1. 1. Identify the current version of Hi.Events running in your environment
  2. 2. If the current version is before 1.11.0, plan an upgrade to version 1.11.0 or later
  3. 3. Before upgrading, review the release notes for version 1.11.0 to understand any changes
  4. 4. Perform the upgrade following the project's standard upgrade procedure
  5. 5. After upgrading, verify that hidden tickets cannot be purchased without proper authorization

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60118 — 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-60118 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