Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-57960 medium CVSS 6.5

Vulnerability in Hi.Events (CVE-2026-57960)

Summary

Vulnerability in Hi.Events (CVE-2026-57960). Confidential information can be exposed externally. Exploitable via GET /api/public/check-in-lists/{short_id}/attendees.

Original description

The description as published by the source.

Hi.Events through 1.9.0 public check-in list endpoints use short_id as sole access control, allowing unauthenticated access to retrieve full attendee lists including emails and personal information. Attackers with knowledge of the short_id can call GET /api/public/check-in-lists/{short_id}/attendees to read attendee data and create or delete check-in records without authentication.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-57960 has been found in Hi.Events.
Attackers can target a specific entry point like GET /api/public/check-in-lists/{short_id}/attendees over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Hi.Events CVE-2026-57960" on the vendor's site.

CVE-2026-57960 (Hi.Events) — CWE-359 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/public/check-in-lists/{short_id}/attendees
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-359) exists in Hi.Events. Attackers reach the vulnerable code path via GET /api/public/check-in-lists/{short_id}/attendees without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Hi.Events. Attack surface: GET /api/public/check-in-lists/{short_id}/attendees.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/public/check-in-lists/{short_id}/attendees requests with malformed payloads or SQL meta-characters. Run grep -r 'Hi.Events' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Hi.Events' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Hi.Events を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/public/check-in-lists/{short_id}/attendees' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/public/check-in-lists/{short_id}/attendees への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against GET /api/public/check-in-lists/{short_id}/attendees on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details