CVE-2026-18028: pretix · Insecure Direct Object Reference
Affects pretixSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low · fixed in 2026.6.1 : update pretix when convenient.
Data as of 28 Oct 2026, 05:11 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.6.1, 2026.5.4, 2026.4.6
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade pretix to 2026.6.1, 2026.5.4 or 2026.4.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pretix GmbHpretix | Affected
| Fixed in
|
| pretix GmbHpretix | Affected
| Fixed in
|
| pretix GmbHpretix | Affected
| Fixed in
|
GitHubpretixpkg:github/pretixOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict access to the quick setup functionality to trusted users only and monitor for unusual configuration changes. Avoid granting unnecessary permissions to users during event setup.
Description
The "quick setup" view presented to users after they first create an event allows to set up the most critical parts of an event in just a few clicks. This view did not properly check that the user has permission to change configuration for the given event. An attacker could use a well-timed request to create products, quotas, set bank transfer configuration, or connect a stripe account to an event they do not have access to.