Pretix vulnerabilities, page 2

49 vulnerabilities

Known vulnerabilities in Pretix products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 23 products.

RoutineCVE-2026-101266pretixCheckout validation bypassA logic flaw in the checkout flow allows users to bypass validations performed during the check-in by skipping entire check-in steps.CVSS1.3LowEPSS0.27%RoutineCVE-2026-82838pretix · venuelessDefault webserver configuration with incorrect CSPThe default docker image shipped for Venueless did not properly ensure that uploaded SVG files could not be delivered with executable JavaScript content. A valid Content Security Policy is now set.CVSS6.4MediumEPSS0.40%RoutineCVE-2026-13602pretix +7 moreSession takeover vulnerabilityWe 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.CVSS7.7HighEPSS0.38%PrioritiseCVE-2026-13603pretix · pretix-oppwaSSRF with API key leak in pretix-oppwaThe payment integration pretix-oppwa provides support for the payment providers VR Payment, Hobex, and potentially others based on Oppwa's technology. The integration of Oppwa, following their official documentation, includes a step where the user is redirected from the payment provider back to our system with a query parameter like ?resourcePath=/v1/checkouts/{checkoutId}/payment in the URL. Our system is then supposed to fetch the status of the transaction from the URL given by baseUrl + resourcePath. Our plugin pretix-oppwa did so insecurely by concatenating the parameter form the URL to the base domain of the API without further validation and, critically, without a / at the end of the baseUrl. Therefore, an attacker could inject a resourcePath argument in a way that causes pretix to call a different server instead. Since the request includes the access token (API key) of the Oppwa account, this would leak the access token, giving access to data contained in the payment provider's system. This is fixed with the release today by strictly validating the given API URL. After installing the update, we recommend asking your payment provider for a new access token and updating it in pretix.CVSS9.0CriticalEPSS0.41%RoutineCVE-2026-13350pretix · venuelesspretix venuelessPermissions where checked incorrectly during room creation, allowing attackers to create rooms of types they shouldn't be allowed to create.CVSS2.3LowEPSS0.27%RoutineCVE-2026-57532pretixpretix pretixMalicious HTML content contained in the layout specification of a PDF ticket or badge layout was executed when the PDF editor is opened in the browser. This could allow one backend user to inject JavaScript into the browser context of another backend user. Due to requirements of the PDF rendering and editing libraries used, this is one of the few pages in our backend that do not have a strong Content-Security-Policy that would render this capability useless for most scenarios.CVSS8.8HighEPSS0.43%RoutineCVE-2026-57533pretixpretix pretixMalicious HTML content could be injected into the page pretix shows when redirection to an untrusted page occurs. Since this page has a Content-Security-Policy, this can mainly be used for phishing purposes.CVSS2.1LowEPSS0.29%RoutineCVE-2026-57535pretixpretix pretixContent injected to PDF rendering contexts could, in many places, include HTML content including <img> tags. If the src attribute of these images pointed to an URL, the PDF rendering engine would download the image from that place and display it, thereby leaking information about the rendering server and possibly creating an SSRF vector in the local network.CVSS2.1LowEPSS0.40%RoutineCVE-2026-13225pretixStored XSS in ticket confirmation pageMalicious HTML content could be injected into the email address of an order, which pretix showed without sanitization on the confirmation page for individual tickets in that order.CVSS5.3MediumEPSS0.44%RoutineCVE-2026-57534pretix · pretix-pagesStored XSS in pretix-pagesMalicious HTML content could be injected into the content of a page in the pretix-pages plugin.CVSS2.1LowEPSS0.43%RoutineCVE-2026-57536pretix · pretix-mollieInsufficient validation of payment status in pretix-mollieOur payment integration with Mollie did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment.CVSS6.3MediumEPSS0.33%RoutineCVE-2026-13222pretix · pretix-oppwaInsufficient validation of payment status in pretix-oppwaOur payment integration with Oppwa-based payment methods did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment.CVSS6.3MediumEPSS0.33%RoutineCVE-2026-13223pretix · pretix-computopInsufficient validation of payment status in pretix-computopOur payment integration with Computop-based payment methods did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment.CVSS6.3MediumEPSS0.33%RoutineCVE-2026-13314pretix · pretix-digitalStored XSS in pretix-digitalMalicious HTML content could be injected into the content rendered by the pretix-digital plugin.CVSS2.0LowEPSS0.43%RoutineCVE-2026-12863pretix · venuelessOpen redirectAn unvalidated redirect was contained in Venueless' social login functionality and could be exploited for phishing using trusted domains.CVSS5.1MediumEPSS0.35%RoutineCVE-2026-12862pretix · venuelessXLSX formula injection in exportsUntrusted user data was passed verbatim to Excel exports for administrators. This allowed formula injection which can be used to compromise the environment of the user loading the file or other data in the file.CVSS5.1MediumEPSS0.38%RoutineCVE-2026-11764pretixData exposed without proper permissionWhen creating an export of all reusable media, the secrets of connected gift cards were included in the export even if the user creating the export does not have permission to view gift cards. This is inconsistent with the UI and API where only the first letters of the gift card secret are shown. Therefore, it allows circumventing a permission boundary.CVSS3.6LowEPSS0.23%RoutineCVE-2026-9712pretix +1 moreInsecure direct object referenceWhen creating an export through the pretix API, API clients are returned an UUID value for their export job (a long, random string like 35742818-c375-4d15-839f-d49aecce94d6). Using this UUID, the API client can then request the actual file for download. The same kind of UUID is used in other places in pretix when temporary files are generated for internal use or download. One remaining API endpoint, however, wrongfully did not verify if the UUID used for download actually belongs to a file that is supposed to be downloadable and belongs to the correct user. In reality, this is hard to exploit because an attacker would need to have access to a valid UUID for the file they desire which is unlikely to happen without a separate security problem giving them access to logs etc.CVSS3.8LowEPSS0.22%RoutineCVE-2026-5600pretix +1 morepretix pretixA new API endpoint introduced in pretix 2025 that is supposed to return all check-in events of a specific event in fact returns all check-in events belonging to the respective organizer. This allows an API consumer to access information for all other events under the same organizer, even those they should not have access to. These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example: { "id": 123, "successful": true, "error_reason": null, "error_explanation": null, "position": 321, "datetime": "2020-08-23T09:00:00+02:00", "list": 456, "created": "2020-08-23T09:00:00+02:00", "auto_checked_in": false, "gate": null, "device": 1, "device_id": 1, "type": "entry" } An unauthorized user usually has no way to match these IDs (position) back to individual people.CVSS5.5MediumEPSS0.26%RoutineCVE-2026-5599pretix · venuelessAPI allows deletion of users of other instanceA user with API access and "manage users" permission in any venueless world is able to trigger deletion of user accounts in other worlds.CVSS7.3HighEPSS0.23%