Unauthenticated attendee PII exposure via check-in capability URL
Published Jun 29, 2026 · Updated Jun 29, 2026
Improper access control in Hi.Events 1.9.0 and earlier allows remote attackers to read attendee PII through public check-in URLs. Public check-in routes lack authentication middleware, and AttendeeWithCheckInPublicResource returns email, name, and order identifiers using short_id as the sole access control. Knowledge of the 77-bit short_id is required; remote attackers who obtain it can read an event's attendee list and create or delete check-in records without authentication.
Summary
What happened
Improper access control in Hi.Events 1.9.0 and earlier allows remote attackers to read attendee PII through public check-in URLs. Public check-in routes lack authentication middleware, and AttendeeWithCheckInPublicResource returns email, name, and order identifiers using short_id as the sole access control. Knowledge of the 77-bit short_id is required; remote attackers who obtain it can read an event's attendee list and create or delete check-in records without authentication.
The record
- CVE
- CVE-2026-57960
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- Hi.Events
- Product
- Hi.Events
- Classifications
- CWE-359, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 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.9.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
- Upstream issue reproduction for public check-in endpointsproof 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