Unauthorized hidden-ticket purchase via missing visibility validation
Published Jul 14, 2026 · Updated Jul 14, 2026
Missing authorization in Hi.Events before 1.11.0 allows remote attackers to purchase hidden tickets through the public checkout API. OrderCreateRequestValidationService accepts attacker-supplied product and price IDs without rejecting hidden or promo-only inventory. No authentication is required; sequential IDs can be inferred from visible tickets, enabling purchases of VIP, invite-only, or discounted inventory.
Summary
What happened
Missing authorization in Hi.Events before 1.11.0 allows remote attackers to purchase hidden tickets through the public checkout API. OrderCreateRequestValidationService accepts attacker-supplied product and price IDs without rejecting hidden or promo-only inventory. No authentication is required; sequential IDs can be inferred from visible tickets, enabling purchases of VIP, invite-only, or discounted inventory.
The record
- CVE
- CVE-2026-60118
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Hi.Events
- Product
- Hi.Events
- Classifications
- CWE-284, CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.11.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory checkout-request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo