When changing the settings of a scheduled export, no permission checks are done to see whether the user making the
Source GCVE Database
Public exploit available · CVSS 5.1 Medium · fixed in 2026.9.2 : patch pretix as a priority.
Data as of 17 Nov 2026, 17:04 UTC
Thin evidence
One scorer or none| CNA (pretix) | CVSS 4.0 | 5.1 |
|---|
- Patch
- Available – fixed in 2026.9.2, 2026.8.3, 2026.7.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:L/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade pretix to 2026.9.2, 2026.8.3 or 2026.7.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pretixpretix | Affected
| Fixed in
|
| pretixpretix | Affected
| Fixed in
|
| pretixpretix | 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
A fix is available that disallows changing the export type of existing scheduled exports, thereby enforcing permission checks. This fix is a breaking API change but is not expected to affect typical API usage. Users should apply this fix to prevent unauthorized access escalation via scheduled export settings.
Description
A vulnerability exists in the scheduled export settings functionality where no permission checks are performed when changing the export type. This allows an attacker with permission to change organizer settings and access certain data (e.g., orders) to modify the export to access other data (e.g., gift cards) without proper authorization. The fix involves disallowing changes to the export type of existing scheduled exports, which is a breaking API change but expected to have minimal impact on typical API usage.