CVE
pretix permission bypass in scheduled export editing
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:P
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.7.5, 2026.8.3, 2026.9.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.7.5, 2026.8.3, 2026.9.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 100% of pretix downloads last week were affected versions (7.1K).PyPI, per-version counts from ClickPy, 7.1K downloads in the last 7 days, read Nov 14, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In pretix, a logged-in user with high privileges who can change organizer settings and already has access to orders can edit a scheduled export to pull gift card data, even without access to gift cards. The attack can be carried out over the network, but only by an account with those high privileges.
Written by a model from the sources below. Verify against them.
Original description
When changing the settings of a scheduled export, no permission checks are done to see whether the user making the change has access to the exporter after the change. This way, an attacker with access to change organizer settings and e.g. access to all orders could change the export to refer to gift cards instead, even if they do not have access to gift cards.
The fix for this is technically a breaking API change, since changing the export type of existing scheduled exports is no longer allowed, but we don't expect this to affect any typical API usage.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects PyPI packages
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Impact
- Widely used
pretix has 1.7k weekly downloads.Source: pypistats.org
11 packages depend on pretix.Source: deps.dev
What to do
Upgrade to a fixed version: 2026.7.5, 2026.8.3, 2026.9.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127174 (Permission bypass through editing scheduled exports), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127174 (entry last updated 2026-11-17):
Affected:
- PyPI package pretix: fixed in 2026.7.5; from 2026.8.0, fixed in 2026.8.3; from 2026.9.0, fixed in 2026.9.2
Fixed versions: 2026.7.5, 2026.8.3, 2026.9.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127174 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127174 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://pretix.eu/about/en/blog/20261117-release-2026-9-2-pretixscan-wordpress-widget/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127174
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127174"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- pretixPyPI
fixed in 2026.7.5; From 2026.8.0 · fixed in 2026.8.3; From 2026.9.0 · fixed in 2026.9.2
No fix released. The advisory names 2026.7.5 and 2026.8.3 and 2026.9.2 as the fix, which the registry doesn't have yet. The latest release, 2026.9.1, is still affected.
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127174
Is CVE-2026-127174 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-127174?
pretix (PyPI): before 2026.7.5; from 2026.8.0 before 2026.8.3; from 2026.9.0 before 2026.9.2.Source: cve.now feed data
How do I fix CVE-2026-127174?
Upgrade to a fixed version: 2026.7.5, 2026.8.3, 2026.9.2.Source: cve.now feed data