Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAuthenticate to pretix backend with low-privilege event access
-
DeliveryCraft link abusing Referer-redirect signing oracle
-
ExploitObtain valid signature over arbitrary session parameters
-
InstallInject signed blob into payment plugin session transport
-
C2Write attacker-chosen parameters into own session
-
ExecuteAbuse admin act-as feature guessing target user ID
-
ImpactAssume any user identity and access all data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the attacker to already hold authenticated access to at least one event in the pretix backend (CVSS PR:L), so this is an insider/multi-tenant escalation, not remote-unauthenticated. Concrete prerequisites: (1) at least one of the affected payment plugins (or bundled Stripe) must be present so the unvalidated signed-session-parameter transport code path exists; (2) the core Referer-obfuscation redirect feature must be reachable to serve as the signing oracle that reuses the shared key/salt; and (3) the core admin "act on behalf of" impersonation feature must be usable, with the attacker guessing a valid target user ID. Limiting factors: the need for an existing backend account bounds the attacker population; the impact is greatest on shared or SaaS instances with many low-trust organizers, and much lower on single-tenant deployments where the operator is already fully trusted. No end-user interaction is required (UI:N). |
| Impact | The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N with High confidentiality/integrity/availability on both vulnerable and subsequent systems) scores 7.7 and is internally consistent with the described impact: a network-reachable, low-complexity chain that requires only low privileges (access to at least one event in the backend) and no user interaction, yielding full account takeover. The E:U flag (Exploit Unproven) means no public exploit is identified at time of analysis, and there is no CISA KEV listing and no EPSS value provided - so despite the high severity there is no signal of active or automated exploitation. The most important qualifier is PR:L: this is not a pre-auth internet-wide risk but an insider/multi-tenant escalation, most dangerous on shared/SaaS pretix deployments where many low-trust organizers share one backend. The realism is high (the vendor describes a concrete, working three-stage chain and shipped fixes), but the barrier of already needing a backend event account meaningfully narrows the attacker population. Note: no independent confirmation of exploitability beyond the vendor blog; treat exploit maturity as unproven rather than absent. |
| Exploit ScenarioDerived | A malicious event organizer with a legitimate low-privilege backend account on a shared pretix instance crafts links against the Referer-obfuscation redirect feature to have the server cryptographically sign arbitrary session parameters, then injects that signed blob into a payment plugin's session-transport path, which accepts it because only the signature is checked. Having written attacker-controlled parameters into their own session, they invoke the admin "act on behalf of" impersonation feature and guess a target user ID to switch into any account and read all its data. No public exploit is identified at time of analysis, but the network vector and low attack complexity (AV:N/AC:L) make the chain straightforward for an attacker who already holds backend access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Privilege escalation to full account takeover in pretix (open-source event ticketing) and its payment integration plugins (Stripe, pretix-mollie, pretix-oppwa, pretix-bitpay, pretix-payone, pretix-secuconnect, pretix-sofort, pretix-saferpay) lets an authenticated backend operator become any user and read any data in the system. The flaw chains three weaknesses: a signed-session-parameter transport path with no scope validation, a signing-oracle reuse of the same key/salt in an unrelated Referer-obfuscation redirect, and the admin "act on behalf of" impersonation feature. No public exploit is identified at time of analysis (CVSS 4.0 carries E:U, exploit unproven), but the vendor fixed all affected components in releases published 2026-07-01.
RemediationAI
Patch available per vendor advisory: upgrade the pretix core to the release issued 2026-07-01 (release 2026.5.3, https://pretix.eu/about/en/blog/20260701-release-2026-5-3/) and simultaneously update every installed affected payment plugin (pretix-mollie, pretix-oppwa, pretix-bitpay, pretix-payone, pretix-secuconnect, pretix-sofort, pretix-saferpay) to their same-day fixed releases, since core and plugins were patched in a coordinated set and a partial upgrade leaves the chain intact. The fixes strictly validate that no session parameters outside a plugin's own scope may be set, assign distinct signature salts per plugin and feature to remove the signing-oracle reuse, and require unguessable session information before the admin impersonation feature will switch users. If immediate patching is impossible, the strongest compensating control is to tightly restrict who holds backend event access, since exploitation requires an authenticated organizer account (PR:L) - audit and remove untrusted or dormant staff/organizer accounts on shared instances; on multi-tenant SaaS deployments this is especially urgent because any low-privilege tenant is a potential attacker. Exact per-plugin fixed version strings should be confirmed directly from the advisory before deployment.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 8 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
pretix is a Django-based, self-hostable and SaaS event ticketing platform; the affected surface spans the core system and eight payment-provider plugins listed in the CPE set (cpe:2.3:a:pretix:pretix and the pretix-mollie/oppwa/bitpay/payone/secuconnect/sofort/saferpay plugins, with Stripe bundled in core). The root cause maps to CWE-20 (Improper Input Validation): a code path meant to carry session parameters from a cookie-isolated tab (e.g. the embeddable pretix widget) to a new tab passes a cryptographically signed parameter blob but validates only the signature - never that the parameters fall within the plugin's legitimate scope. Cryptographic signing here is used as an integrity/authenticity gate, but because a separate core feature (redirect links that strip Referer headers to avoid leaking URL secrets) reused the identical signing key AND salt, that redirect endpoint becomes a signing oracle that will sign attacker-chosen content. Django's signing framework separates trust domains by salt, so sharing a salt across two features collapses them into one forgeable trust domain.
Know when Pretix gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U
Network-reachable and low-complexity but requires an existing backend event account (PR:L); becoming any user crosses a privilege boundary (S:C) with full C/I/A compromise.
Primary rating from Vendor (rami.io).
CVSS VectorVendor: rami.io
Lifecycle Timeline
1DescriptionCVE.org
We found a chain of combining multiple weaknesses in the product that could allow an attacker to become any user in the backend and access any data:
*
The payment integration plugins Stripe (included in the core system), pretix-mollie, pretix-oppwa, pretix-bitpay, pretix-payone, pretix-secuconnect, pretix-sofort, and pretix-saferpay contain a code path that is intended for the transport of session parameters from a tab with isolated cookies (e.g. in the pretix widget) to a new tab. For this purpose, a set of session parameters is cryptographically signed and then passed to the new tab as a URL parameter. The plugins perform no further validation of the session parameters, other than the cryptographic signature being valid. This is fixed with the releases issued today by strictly validating that no session parameters outside of the scope of the respective plugin may be set.
*
An unrelated feature in the core system is used to generate redirect links that obfuscate any Referer headers for outgoing links to prevent leakage of secrets in URLs. This redirect page also requires cryptographically signed parameters. Unfortunately, it uses the same key and salt for the signature as the previously mentioned feature in the payment integration plugins. A motivated attacker with access to at least one event in the backend can trick the system into cryptographically signing arbitrary content using specially crafted links. In combination with the previous issue, the attacker could use this to set and modify arbitrary parameters on their user session by injecting the signed parameters into the feature of the payment providers. This is fixed with the releases issued today by using different salts for the signature for each plugin and feature.
*
A third, unrelated feature in the core system is used for admin users to act on behalf of another user, mostly for debugging purposes. With being able to insert arbitrary parameters into a session, an attacker can abuse this feature to change their session from their actual user to any user in the system by guessing a valid user ID. This is fixed with the release today by requiring unguessable information to be contained in the session of the user to switch to.
Executive ViewAI
Pretix event ticketing systems and integrated payment processors contain a critical privilege-escalation chain allowing authenticated backend operators to hijack any user account and access all system data. For ticketing operators, this creates insider-threat exposure through revenue fraud, customer data compromise, and regulatory violations. While no public exploit identified at time of analysis, vendors released patches on 2026-07-01.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
pretix before 2024.1.1 mishandles file validation. Rated critical severity (CVSS 9.8), this vulnerability is remotely ex
Server-side URL manipulation in the pretix-oppwa payment plugin (fixed in pretix 2026.5.3) lets a remote attacker exfilt
Stored cross-site scripting in Pretix's PDF ticket and badge layout editor allows one backend user to inject JavaScript
pretix before 2023.7.2 allows Pillow to parse EPS files. Rated high severity (CVSS 7.8), this vulnerability is no authen
rami.io pretix before 4.17.1 allows OAuth application authorization from a logged-out session. Rated high severity (CVSS
Venueless instances allow authenticated users with 'update world' permissions to exfiltrate chat messages from direct me
Cross-world user deletion in venueless allows authenticated API users with 'manage users' permission in one world to del
Stored XSS in organizer and event settings of pretix up to 2024.7.0 allows malicious event organizers to inject HTML tag
Information disclosure in Pretix email template processing allows authenticated backend users to extract sensitive syste
Information disclosure in Pretix email template processing allows authenticated backend users to extract sensitive syste
Payment status replay in pretix-mollie allows unauthenticated attackers to obtain multiple valid event tickets by reusin
Payment response replay vulnerability in the pretix-oppwa integration allows a remote attacker to reuse a legitimate Opp
EUVD-2026-40995
GHSA-q93m-6jvc-jc45
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB