Vendor
pretix
40 known vulnerabilities.
pretix at a glance
- Last 12 months
- 39
- Critical · all time
- 1
- Exploited · all time
- 0
- Public exploit · all time
- 0
Show as table
| Month | Vulnerabilities | Critical |
|---|---|---|
| Nov 2026 | 2 | 0 |
| Oct 2026 | 3 | 0 |
| Sep 2026 | 6 | 0 |
| Aug 2026 | 1 | 0 |
| Jul 2026 | 4 | 1 |
| Jun 2026 | 13 | 0 |
| May 2026 | 1 | 0 |
| Apr 2026 | 2 | 0 |
| Mar 2026 | 1 | 0 |
| Feb 2026 | 3 | 0 |
| Jan 2026 | 0 | 0 |
| Dec 2025 | 2 | 0 |
| Nov 2025 | 1 | 0 |
| Oct 2025 | 0 | 0 |
| Sep 2025 | 0 | 0 |
| Aug 2025 | 0 | 0 |
| Jul 2025 | 0 | 0 |
| Jun 2025 | 0 | 0 |
| May 2025 | 0 | 0 |
| Apr 2025 | 0 | 0 |
| Mar 2025 | 0 | 0 |
| Feb 2025 | 0 | 0 |
| Jan 2025 | 0 | 0 |
| Dec 2024 | 0 | 0 |
Products
40 results · Feed
-
Low 1.2
Missing permission check in ticket layout API
Our API endpoint for changing ticket layouts did not properly check permissions of the requesting user or API token. An attacker with read-only access to an event could use this to change the event's ticket layout.
-
Medium 6.3
Insufficient validation of payment status in pretix-adyen
Our 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 wi…
-
Low 2.3
Incorrect session validation for API-created shredder exports
The mechanism binding files generated during a shredding process to the authentication method is not working correctly and the same session token is used for all token-based API users. This is similar to an issue fixed in 2026.7.1 but was missed while creatin…
-
Medium 6.9
When pretix is used as the identity provider in a Single-Sign-On (SSO) setup for customer accounts, the system did not …
-
Medium 5.3
Giftcard enumeration
Some of our API endpoints allowed to create order payments referencing a gift card by using the auto-incremented internal ID. This ID was not checked and allowed creating payments that reference gift cards from different organizers and thereby obtaining their…
-
Low 2.1
OAuth credentials not disabled when application is disabled
OAuth credentials (access tokens) are valid for the entirety of their lifetime, even if the application (OAuth client) they are bound to is manually disabled.
-
Low 2.1
HTML injection
Malicious HTML content could be injected into the help texts of various fields with organizer permissions.
-
Low 2.3
Incorrect session validation for API-uploaded files
The 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 …
-
Low 1.7
Customer session fixation
If 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 attac…
-
Low 2.7
Revenue information leak
A 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.
-
Low 1.3
Checkout validation bypass
A logic flaw in the checkout flow allows users to bypass validations performed during the check-in by skipping entire check-in steps.
-
Medium 6.4
Default webserver configuration with incorrect CSP
The 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.
-
Low 2.3
Missing authorization check in event quick setup view
The "quick setup" view presented to users after they first create an event allows to set up the most critical parts of an event in just a few clicks. This view did not properly check that the user has permission to change configuration for the given event. An…
-
Medium 6.3
Insufficient validation of payment status in pretix-girosolution
Our payment integration with GiroCheckout 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 tic…
-
High 7.7
Session takeover vulnerability
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-bi…
-
Critical 9.0
SSRF with API key leak in pretix-oppwa
The 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 redirect…
-
Low 2.3
Permissions where checked incorrectly during room creation, allowing attackers to create rooms of types they shouldn't …
-
High 8.8
Malicious HTML content contained in the layout specification of a PDF ticket or badge layout was executed when the PDF …
-
Low 2.1
Malicious HTML content could be injected into the page pretix shows when redirection to an untrusted page occurs. Since…
-
Low 2.1
Content injected to PDF rendering contexts could, in many places, include HTML content including <img> tags. If the src…
-
Medium 5.3
Stored XSS in ticket confirmation page
Malicious 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.
-
Low 2.1
Stored XSS in pretix-pages
Malicious HTML content could be injected into the content of a page in the pretix-pages plugin.
-
Medium 6.3
Insufficient validation of payment status in pretix-mollie
Our 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 w…
-
Medium 6.3
Insufficient validation of payment status in pretix-oppwa
Our 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 mul…
-
Medium 6.3
Insufficient validation of payment status in pretix-computop
Our 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 …
-
Low 2.0
Stored XSS in pretix-digital
Malicious HTML content could be injected into the content rendered by the pretix-digital plugin.
-
Medium 5.1
Open redirect
An unvalidated redirect was contained in Venueless' social login functionality and could be exploited for phishing using trusted domains.
-
Medium 5.1
XLSX formula injection in exports
Untrusted 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.
-
Low 3.6
Data exposed without proper permission
When 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 lett…
-
Low 3.8
Insecure direct object reference
When 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 s…
-
Medium 5.5
pretix: API leaks check-in data between events of the same organizer
A 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 u…
-
High 7.3
API allows deletion of users of other instance
A user with API access and "manage users" permission in any venueless world is able to trigger deletion of user accounts in other worlds.
-
High 7.3
Unauthorized access to chat contents
A user with permission "update world" in any Venueless world is able to exfiltrate chat messages from direct messages or channels in other worlds on the same server due to a bug in the reporting feature. The exploitability is limited by the fact that the atta…
-
High 7.5
Unsafe variable evaluation in email templates
Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name} is used in an email template, it will be replaced with the buyer's name for the final email. This mechanism contained a security-relevant bug: It w…
-
High 7.5
Unsafe variable evaluation in email templates
Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name} is used in an email template, it will be replaced with the buyer's name for the final email. This mechanism contained a security-relevant bug: It w…
-
High 7.5
Unsafe variable evaluation in email templates
Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name} is used in an email template, it will be replaced with the buyer's name for the final email. This mechanism contained two security-relevant bugs: *…
-
Low 3.8
Insecure direct object reference
Multiple API endpoints allowed access to sensitive files from other users by knowing the UUID of the file that were not intended to be accessible by UUID only.
-
Low 3.8
Insecure direct object reference
An API endpoint allowed access to sensitive files from other users by knowing the UUID of the file that were not intended to be accessible by UUID only.
-
Low 2.4
Limited HTML injection in emails
Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name} is used in an email template, it will be replaced with the buyer's name for the final email. If the name of the attendee contained HTML or Markdown…
-
High 7.2
Stored XSS in Placeholder Samples in Mail Preview
Stored XSS in organizer and event settings of pretix up to 2024.7.0 allows malicious event organizers to inject HTML tags into e-mail previews on settings page. The default Content Security Policy of pretix prevents execution of attacker-provided scripts, mak…