Pretix vulnerabilities
49 vulnerabilities
Known vulnerabilities in Pretix products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 23 products.
Products
23- Pretix29 vulnerabilities
- Venueless8 vulnerabilities
- Pretix Oppwa3 vulnerabilities
- Pretix Adyen2 vulnerabilities
- Pretix Mollie2 vulnerabilities
- Pretixscan Proxy2 vulnerabilities
- Double Opt In Step1 vulnerabilities
- Newsletters1 vulnerabilities
- Pretix Widget Wordpress Plugin1 vulnerabilities
- Pretix Bitpay1 vulnerabilities
- Pretix Computop1 vulnerabilities
- Pretix Digital1 vulnerabilities
- Pretix Doistep1 vulnerabilities
- Pretix Newsletter1 vulnerabilities
- Pretix Offlinesales1 vulnerabilities
- Pretix Pages1 vulnerabilities
- Pretix Payone1 vulnerabilities
- Pretix Saferpay1 vulnerabilities
- Pretix Secuconnect1 vulnerabilities
- Pretix Sofort1 vulnerabilities
- Pretixscan Android1 vulnerabilities
- Pretixscan Desktop1 vulnerabilities
- Pretixscan Ios1 vulnerabilities
RoutineCVE-2026-131171pretix · venuelessRoom and world premissions not clearly separatedA bug caused room permissions to leak into the world permissions of the acting user during certain actions.CVSS5.3MediumRoutineCVE-2026-131163pretix · pretix-adyenStored XSS in pretix-adyenA stored XSS in pretix-adyen has been discovered where an attacker could configure his own ticket shop in a way that API calls are not made to Adyen, but an attacker-controlled server. Results of these API calls would then be embedded in a part of the shop without proper escaping, leading to full XSS including potential session takeover.CVSS8.6HighRoutineCVE-2026-131165pretixIncorrect check of permissions in scheduled exportsThe fix for CVE-2026-127174 published in 2026.9.2 is incomplete: When expanding an export from "some events" to "all events", it is checked that the acting user is part of a team with permission to all events, but this check is not correctly bound to the organizer and could also be passed through permissions on a different organizer.CVSS2.1LowRoutineCVE-2026-131169pretixPermissions are copied when copying scheduled exportsWhen a scheduled export is copied, the permissions of the original export's owner are used when running the export. This allows users to create exports with data they usually shouldn't be able to see, but only within events they already have permissions to.CVSS2.1LowRoutineCVE-2026-131164pretixLink to parent order or ticket exposed in certain conditionsWhen a ticket holder opens the ticket page of a ticket that is an add-on (possible since 2026.9) the HTML content of the page contains the secret link to the parent product, creating a potential data leak. Under different specific conditions, when a ticket contains user-uploaded files in response to a question, the page can even contain the secret link to the entire order.CVSS2.3LowRoutineCVE-2026-131168pretixValidation bypass allows buying sold-out productsA legacy code path allowed users to craft requests to a ticket shop that bypass some validation steps for the selected products. In consequence, this could lead to an attacker purchasing products that are in fact sold out.CVSS6.6MediumRoutineCVE-2026-131170pretixInsufficient validation of payment status for StripeOur payment integration with Stripe 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. However, the attack requires knowledge of a valid charge ID from the same event which we believe is usually not exposed to users.
To simplify attack surface, the fix removes support for incoming webhooks regarding payments created through Stripe's old "source" API. pretix stopped creating payments using this API in 2024.1 for most payment methods and in 2024.9 for all payment methods.CVSS6.3MediumRoutineCVE-2026-131166pretixIncorrect device security profileWhen configuring a device to use the security profile "pretixSCAN (kiosk mode, no order sync, no search)", the API search endpoint introduced in pretix 4.12 was not blocked correctly. This theoretically allows these devices to perform searches for orders even if that was not intended. If the device is in kiosk mode, the search button will still be hidden from users.CVSS6.0MediumPrioritiseCVE-2026-131167pretixUnsafe usage of return valuespretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to.CVSS8.9HighRoutineCVE-2026-130608pretix · venuelesspretix venuelessWhen using the admin area profile form to change ones profile details *except* the password (so, email or username), the password field in the database is overwritten with the plaintext password. Further login is not possible, so the error is noticeable, but the password is leaked to the database.CVSS8.1HighEPSS0.35%RoutineCVE-2026-127174pretixPermission bypass through editing scheduled exportsWhen changing the settings of a scheduled export, no permission checks are done to see whether the user making the change has access to the exporter after the change. This way, an attacker with access to change organizer settings and e.g. access to all orders could change the export to refer to gift cards instead, even if they do not have access to gift cards.
The fix for this is technically a breaking API change, since changing the export type of existing scheduled exports is no longer allowed, but we don't expect this to affect any typical API usage.CVSS5.1MediumEPSS0.30%RoutineCVE-2026-127140pretix · pretix widget wordpress pluginServer-Side Request Forgery in pretix Widget WordPress pluginOur WordPress plugin for the pretix Widget performs HTTP calls to pre-fetch CSS and JS files into a local cache and stores them publicly on the WordPress instance. These HTTP calls are made with wp_remote_get, not wp_safe_remote_get, and therefore allow SSRF with body extraction. Exploiting this requires sufficient WordPress permissions to create or modify pages.CVSS3.8LowEPSS0.27%RoutineCVE-2026-127139pretix · pretixscan proxyInsecure device token generation in pretixSCAN ProxypretixSCAN Proxy does not use a secure random generator to generate initialization tokens and API keys for the connection between pretixSCAN devices and the pretixSCAN Proxy. This could allow a skilled attacker with access to at least some of the tokens to predict the value of other tokens more easily.
pretixSCAN is usually used on local networks and the level of exposure heavily depends on the structure of that network. If you want to be extra careful, it might make sense to reconnect your devices to the proxy after the update.CVSS4.4MediumEPSS0.12%RoutineCVE-2026-127138pretix · pretixscan android +3 moreCircumvention of offline barcode revocation check in pretixSCANpretix provides a mechanism where ticket QR codes are cryptographically signed and can be verified by our pretixSCAN apps in offline mode without any database of valid tickets. pretixSCAN checks the signature to verify that the ticket was issued by the correct pretix event and compares the QR code against a list of revoked QR codes. A QR code becomes revoked when the order is canceled, or the ticket is changed in a way that a new QR code needs to be generated.
However, the parsing of the QR code in all of our pretixSCAN apps contained a faulty computation, rendering the check for the correct length of the contents faulty. This way, an attacker is able to craft multiple QR codes for the same ticket which have the same content, but look different and therefore do not match against the revocation list. This does not allow to fabricate entirely new tickets, but it does allow to enter the event with e.g. a canceled ticket. This attack requires pretixSCAN to be scanning in offline mode and the "pretix signature scheme 1" to be used for the event's QR codes.
If the attack is executed, the ticket unfortunately shows as valid (green) on the scanner but as invalid (red) on the server since the server later cannot match it to a ticket. We scanned the entire database of scans on pretix Hosted and could not find any traces of this being exploited in the past.CVSS6.8MediumEPSS0.11%RoutineCVE-2026-101275pretix · pretix-adyenInsufficient validation of payment status in pretix-adyenOur payment integration with Adyen 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.12%RoutineCVE-2026-101271pretixOAuth credentials not disabled when application is disabledOAuth credentials (access tokens) are valid for the entirety of their lifetime, even if the application (OAuth client) they are bound to is manually disabled.CVSS2.1LowEPSS0.17%RoutineCVE-2026-101270pretixHTML injectionMalicious HTML content could be injected into the help texts of various fields with organizer permissions.CVSS2.1LowEPSS0.18%RoutineCVE-2026-101269pretixIncorrect session validation for API-uploaded filesThe mechanism binding API-uploaded files to the uploader's authentication method is not working correctly and the same session token is used for all token-based API users. Since API-uploaded files are refered to by randomly generated UUIDs and only exist for a day, there is virtually no risk, but it renders the added protection mechanism useless.CVSS2.3LowEPSS0.22%RoutineCVE-2026-101268pretixCustomer session fixationIf an attacker is able to convince a victim on a specially crafted link, the victim is logged in to the attacker's customer account. If the victim does not notice this, this might lead to their order details being stored into the attacker's account. The attack only works when the event is available on a different domain than the organizer page.CVSS1.7LowEPSS0.20%RoutineCVE-2026-101267pretixRevenue information leakA missing permission check allowed low-privileged users with access to an event but without access to the event's orders to extract some specific information. This information includes the number of attendees and the total revenue.CVSS2.7LowEPSS0.24%