Skip to main content

Threat Intelligence Database

Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Package: pkg:github/hieventsdev/Hi.Events

Threat Intelligence

Click on any threat for detailed analysis and mitigation recommendations

CVE-2026-76838 is a Server-Side Request Forgery (SSRF) vulnerability in HiEventsDev's Hi.Events product. The vulnerability arises because webhook destination URLs are only validated at registration, not at dispatch. The validation uses gethostbyname() to reject private and reserved IP ranges, but this check can be bypassed by redirects to internal addresses or by changing DNS records after registration. The server follows redirects by default and returns the internal response body to the requester, exposing potentially sensitive internal services. Version 1.11.1-beta addresses these issues by revalidating URLs at dispatch, pinning validated addresses, checking each redirect hop, and decoding IPv6 transition addresses to prevent bypasses.

Join the discussion

Hi.Events before 1.11.0 contains a cross-site scripting vulnerability that allows authenticated attackers with event creation or edit permissions to inject arbitrary HTML and JavaScript by embedding a malicious event title containing the </script> sequence, which is not escaped by JSON.stringify() when embedded in inline script tags. Attackers can craft an event title that breaks out of the script context in the application/ld+json structured data block or server-side rehydrated state, causing the payload to execute in the browser of any user who views the public event page, including unauthenticated visitors and authenticated administrators.

Join the discussion

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.

Join the discussion

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.

Join the discussion

Hi.Events through 1.9.0 contains a promo code validation vulnerability where reservation validates usage count before asynchronous UpdateEventStatisticsJob increments it, allowing attackers to redeem limited promo codes unlimited times. Attackers can sequentially reserve multiple orders with the same restricted promo code, each reading order_usage_count=0 and passing validation, then complete them all at discounted prices without concurrent requests.

Join the discussion

Hi. Events, an open-source event management platform, contains an SQL injection vulnerability in versions from 0.8.0-beta.1 up to but not including 1.7.1-beta. The vulnerability arises because user-supplied input in the sort_by query parameter is passed directly to the orderBy() function without validation. This affects multiple repository classes and leverages PostgreSQL's support for stacked queries. The issue has been fixed in version 1.

Join the discussion

Showing 1 to 6 of 6 results

Filters:Package: pkg:github/hieventsdev/Hi.Events
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses