VulnerabilityPublished 10 Nov 2026

CVE-2026-125744: Our API endpoint for changing ticket layouts did not properly check permissions of the requesting

Source GCVE Database

Compare

Authoritative record:CVE-2026-125744· Low 1.2

Not known to be exploited · CVSS 1.2 Low · fixed in 2026.9.1 : update pretix when convenient.

Data as of 10 Nov 2026, 18:03 UTC

CVSS 4.0 base score

1.2Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (pretix)	CVSS 4.0	1.2

Patch: Available – fixed in 2026.9.1, 2026.8.2, 2026.7.4

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-p3m5-qw33-fgwv

What to do

Upgrade pretix to 2026.9.1, 2026.8.2 or 2026.7.4.

Affected software

Product	Affected	Fixed in
pretixpretix	Affected >=2026.9.0 <2026.9.1	Fixed in 2026.9.1
pretixpretix	Affected >=2026.8.0 <2026.8.2	Fixed in 2026.8.2
pretixpretix	Affected <2026.7.4	Fixed in 2026.7.4
GitHubpretix`pkg:github/pretix`Other threats	Affected <2026.7.4 >=2026.8.0 <2026.8.2 >=2026.9.0 <2026.9.1	Fixed in 2026.7.4 2026.8.2 2026.9.1

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 read-only access permissions carefully and monitor for unauthorized changes to ticket layouts. Avoid granting unnecessary read-only access to untrusted users or API tokens.

Description

A vulnerability exists in an API endpoint responsible for changing ticket layouts, where the system fails to properly verify the permissions of the requesting user or API token. This flaw allows an attacker with read-only access to an event to modify the event's ticket layout without proper authorization.

Impact

An attacker with read-only access privileges can escalate their capabilities to modify ticket layouts for events, potentially disrupting event configurations or causing unauthorized changes. This could affect event management integrity but does not indicate direct data disclosure or system compromise beyond the ticket layout modification.

Summary

The API endpoint for changing ticket layouts does not correctly enforce permission checks on the requesting user or API token. As a result, an attacker who only has read-only access to an event can exploit this vulnerability to alter the event's ticket layout. This issue was assigned CVE-2026-125744 and has a CVSS 4.0 base score of 5.1, indicating a medium severity level. There is no information about affected versions or available patches, and no known exploits in the wild have been reported.

References

Community reviews

Loading reviews…