# CVE-2026-57959: Hi.Events 1.9.0 - Promo Code Max-Usage Bypass via Asynchronous Job Race Condition


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-m75j-c5ff-9wh8

## What is CVE-2026-57959?

CVE-2026-57959 is a high-severity vulnerability in HiEventsDev Hi.Events, published on 29 Jun 2026. 

### Official description

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.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-57959?


## How do I fix CVE-2026-57959?

No fix has been published for CVE-2026-57959 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57959 being exploited?

There is no known exploitation of CVE-2026-57959 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57959 and fix it if it is affected.

What it is: CVE-2026-57959 is a high-severity vulnerability in HiEventsDev Hi.Events, published on 29 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-57959 in the wild and no public exploit code.

Affected product: HiEventsDev Hi.Events. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57959/ (Markdown: https://insights.sbomify.com/CVE-2026-57959/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57959
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57959
- OSV: https://osv.dev/vulnerability/CVE-2026-57959

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57959/
Summaries are generated and may contain mistakes; the official description above is the record.