Missing permission check in ticket layout API
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.7.4, 2026.8.2, 2026.9.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.7.4, 2026.8.2, 2026.9.1.
- 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? →
- 14/100 · provisional
- 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
Summary
The ticket layout API in this software does not properly check the permissions of the requesting user or API token. An attacker who can reach it over the network and has high-privilege login access can change an event's ticket layout, even if their access to that event is read-only.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Our API endpoint for changing ticket layouts did not properly check permissions of the requesting user or API token. An attacker with read-only access to an event could use this to change the event's ticket layout.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects PyPI packages
- Severity1.2/10CVSS 1.2
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Impact
- Widely used
pretix has 2.3k weekly downloads.Source: pypistats.org
11 packages depend on pretix.Source: deps.dev
What to do
Upgrade to a fixed version: 2026.7.4, 2026.8.2, 2026.9.1.
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-125744 (Missing permission check in ticket layout API), 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-125744 (entry last updated 2026-11-10): Affected: - PyPI package pretix: fixed in 2026.7.4; from 2026.8.0, fixed in 2026.8.2; from 2026.9.0, fixed in 2026.9.1 Fixed versions: 2026.7.4, 2026.8.2, 2026.9.1. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-125744 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125744 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 check_stack from the cve.now MCP server 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/20261110-release-2026-9-1-adyen/ 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-125744 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125744.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- pretixPyPI
fixed in 2026.7.4; From 2026.8.0 · fixed in 2026.8.2; From 2026.9.0 · fixed in 2026.9.1
No fix released. The advisory names 2026.7.4 and 2026.8.2 and 2026.9.1 as the fix, which the registry doesn't have yet. The latest release, 2026.9.0, 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-125744
Is CVE-2026-125744 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-125744?
pretix (PyPI): before 2026.7.4; from 2026.8.0 before 2026.8.2; from 2026.9.0 before 2026.9.1.Source: cve.now feed data
How do I fix CVE-2026-125744?
Upgrade to a fixed version: 2026.7.4, 2026.8.2, 2026.9.1.Source: cve.now feed data