CVE-2026-13602
Session takeover vulnerability
Description
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.
INFO
Published Date :
July 1, 2026, 3:16 p.m.
Last Modified :
July 2, 2026, 6:43 p.m.
Remotely Exploit :
Yes !
Source :
655498c3-6ec5-4f0b-aea6-853b334d05a6
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 4.0 | HIGH | 655498c3-6ec5-4f0b-aea6-853b334d05a6 | ||||
| CVSS 4.0 | HIGH | 655498c3-6ec5-4f0b-aea6-853b334d05a6 |
Solution
- Update payment integration plugins to the latest version.
- Apply core system updates.
- Validate session parameters strictly.
- Use unique salts for cryptographic signatures.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-13602.
| URL | Resource |
|---|---|
| https://pretix.eu/about/en/blog/20260701-release-2026-5-3/ |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-13602 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-13602
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-13602 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-13602 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jul. 01, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-13602', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-07-01T15:26:54.400278Z'} -
New CVE Received by 655498c3-6ec5-4f0b-aea6-853b334d05a6
Jul. 01, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://github.com/pretix/pretix', 'vendor': 'pretix', 'product': 'pretix', 'versions': [{'status': 'affected', 'version': '4.14.0', 'lessThan': '2026.3.5', 'versionType': 'python'}, {'status': 'affected', 'version': '2026.4.0', 'lessThan': '2026.4.5', 'versionType': 'python'}, {'status': 'affected', 'version': '2026.5.0', 'lessThan': '2026.5.3', 'versionType': 'python'}], 'packageName': 'pretix', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}, {'repo': 'https://github.com/pretix/pretix-mollie', 'vendor': 'pretix', 'product': 'pretix-mollie', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '2.5.7', 'versionType': 'python'}], 'packageName': 'pretix-mollie', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}, {'repo': 'https://github.com/pretix/pretix-oppwa', 'vendor': 'pretix', 'product': 'pretix-oppwa', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.4.4', 'versionType': 'python'}], 'packageName': 'pretix-oppwa', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}, {'repo': 'https://github.com/pretix/pretix-bitpay', 'vendor': 'pretix', 'product': 'pretix-bitpay', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.5.3', 'versionType': 'python'}], 'packageName': 'pretix-bitpay', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}, {'repo': 'https://github.com/pretix/pretix-payone', 'vendor': 'pretix', 'product': 'pretix-payone', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.4.3', 'versionType': 'python'}], 'packageName': 'pretix-payone', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}, {'repo': 'https://github.com/pretix/pretix-secuconnect', 'vendor': 'pretix', 'product': 'pretix-secuconnect', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.0.4', 'versionType': 'python'}], 'packageName': 'pretix-secuconnect', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}, {'repo': 'https://github.com/pretix/pretix-sofort', 'vendor': 'pretix', 'product': 'pretix-sofort', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.4.2', 'versionType': 'python'}], 'packageName': 'pretix-sofort', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}, {'repo': 'https://github.com/pretix/pretix-saferpay', 'vendor': 'pretix', 'product': 'pretix-saferpay', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.6.3', 'versionType': 'python'}], 'packageName': 'pretix-saferpay', 'collectionURL': 'https://pypi.python.org', 'defaultStatus': 'unaffected'}] Added Description 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. Added CVSS V4.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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CWE CWE-20 Added CWE CWE-323 Added Reference https://pretix.eu/about/en/blog/20260701-release-2026-5-3/