Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-57960 – Unauthenticated Attendee PII Exposure – Hi.Events through v1.9.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-57960 is a high-severity broken object-level authorization (BOLA) vulnerability in Hi.Events, an open-source self-hosted event management and ticketing platform, affecting all versions through 1.9.0. The flaw allows unauthenticated remote attackers to retrieve full event attendee lists — including names and email addresses — and manipulate check-in records by exploiting public API endpoints that rely solely on a short_id value for access control. The CVSS 4.0 base score is 8.3 (High).

Technical details

  • Root cause: The public check-in list API endpoints lack authentication middleware and use a short_id capability URL as the sole access control mechanism. The AttendeeWithCheckInPublicResource API response exposes sensitive attendee fields — including email addresses, full names, and order identifiers — without requiring any authentication token or API key.
  • Trigger conditions: An attacker must obtain the short_id of a check-in list (e.g., cil_MVHr4rojhEodi). These short IDs are embedded in URLs shared with event volunteers and door staff, creating exposure through browser history, server logs, screenshots, or URL forwarding.
  • Attack vector: Network — the attacker sends unauthenticated HTTP requests to the affected public API endpoints: GET /api/public/check-in-lists/{short_id}/attendees (full attendee list retrieval), POST /api/public/check-in-lists/{short_id}/check-ins (check-in creation), and DELETE /api/public/check-in-lists/{short_id}/check-ins/{check_in_short_id} (check-in deletion).
  • Impact: Full attendee PII — including email addresses, first and last names, order IDs, product IDs, and check-in status — is disclosed to unauthenticated requesters. Additionally, unauthenticated attackers can create or delete check-in records, corrupting event attendance data. Event organizers receive no notification when their attendee data is accessed. This exposure carries potential regulatory implications under data protection frameworks such as GDPR.

Affected software

  • Hi.Events — all versions through 1.9.0 (inclusive)

Severity

  • CVSS 4.0: 8.3 (High) — CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
  • CVSS 3.1: 6.5 (Medium) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Patch: No patched release has been confirmed at the time of this publication. A vendor fix (PR #1229) that removes email addresses and sensitive fields from the unauthenticated public endpoint response is pending merge into the develop branch. Monitor the Hi.Events GitHub repository for a patched release and upgrade immediately upon availability.
  • Workaround: If an immediate upgrade is not possible, restrict network-level access to the /api/public/check-in-lists/ API path via firewall rules or reverse proxy ACLs, limiting access to trusted IP ranges such as known staff or event venue networks. This is especially critical for deployments exposed directly to the internet.
  • Access hygiene: Treat check-in list short_id URLs as sensitive credentials. Limit their distribution to necessary operational staff only, and rotate or invalidate them after each event where feasible.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge