Pretix
by Pretix
Source repositories
CVEs (46)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2024-27447 | Cri | 0.64 | 9.8 | 0.01 | Feb 26, 2024 | pretix before 2024.1.1 mishandles file validation. | ||
| CVE-2026-131167 | Hig | 0.58 | — | 0.01 | Nov 20, 2026 | pretix 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… | ||
| CVE-2026-13603 | Cri | 0.52 | — | 0.00 | Jul 1, 2026 | 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 redirected from the… | ||
| CVE-2026-127138 | Med | 0.44 | — | 0.00 | Nov 17, 2026 | pretix 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… | ||
| CVE-2023-44464 | Hig | 0.44 | 7.8 | 0.00 | Sep 29, 2023 | pretix before 2023.7.2 allows Pillow to parse EPS files. | ||
| CVE-2026-13602 | Hig | 0.43 | — | 0.00 | Jul 1, 2026 | 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,… | ||
| CVE-2026-2452 | Med | 0.42 | 6.5 | 0.00 | Feb 16, 2026 | 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 was possible to… | ||
| CVE-2026-2451 | Med | 0.42 | 6.5 | 0.00 | Feb 16, 2026 | 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 was possible to… | ||
| CVE-2026-101275 | Med | 0.41 | — | 0.00 | Nov 10, 2026 | 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 with only one payment. | ||
| CVE-2026-101274 | Med | 0.38 | — | 0.00 | Oct 28, 2026 | When pretix is used as the identity provider in a Single-Sign-On (SSO) setup for customer accounts, the system did not properly validate the `response_type` requested in an authorization request against the configured grant type of the SSO client. This means that if an SSO… | ||
| CVE-2026-131168 | Med | 0.36 | — | 0.01 | Nov 20, 2026 | A 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. | ||
| CVE-2026-131170 | Med | 0.34 | — | 0.00 | Nov 20, 2026 | Our 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… | ||
| CVE-2026-13223 | Med | 0.34 | — | 0.00 | Jun 25, 2026 | 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 multiple valid … | ||
| CVE-2026-13222 | Med | 0.34 | — | 0.00 | Jun 25, 2026 | 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 multiple valid … | ||
| CVE-2026-127174 | Med | 0.33 | — | 0.00 | Nov 17, 2026 | When 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… | ||
| CVE-2025-13742 | Med | 0.33 | 6.1 | 0.00 | Nov 27, 2025 | 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 formatting, this… | ||
| CVE-2026-131166 | Med | 0.32 | — | 0.00 | Nov 20, 2026 | When 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… | ||
| CVE-2026-2415 | Med | 0.31 | 5.9 | 0.00 | Feb 16, 2026 | 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: * It was… | ||
| CVE-2024-8113 | Med | 0.28 | 5.4 | 0.00 | Aug 23, 2024 | 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, making exploitation… | ||
| CVE-2023-44463 | Med | 0.28 | 5.3 | 0.01 | Oct 2, 2023 | An issue was discovered in pretix before 2023.7.1. Incorrect parsing of configuration files causes the application to trust unchecked X-Forwarded-For headers even though it has not been configured to do so. This can lead to IP address spoofing by users of the application. |
- risk 0.64cvss 9.8epss 0.01
pretix before 2024.1.1 mishandles file validation.
- risk 0.58cvss —epss 0.01
pretix 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…
- risk 0.52cvss —epss 0.00
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 redirected from the…
- risk 0.44cvss —epss 0.00
pretix 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…
- risk 0.44cvss 7.8epss 0.00
pretix before 2023.7.2 allows Pillow to parse EPS files.
- risk 0.43cvss —epss 0.00
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,…
- risk 0.42cvss 6.5epss 0.00
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 was possible to…
- risk 0.42cvss 6.5epss 0.00
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 was possible to…
- risk 0.41cvss —epss 0.00
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 with only one payment.
- risk 0.38cvss —epss 0.00
When pretix is used as the identity provider in a Single-Sign-On (SSO) setup for customer accounts, the system did not properly validate the `response_type` requested in an authorization request against the configured grant type of the SSO client. This means that if an SSO…
- risk 0.36cvss —epss 0.01
A 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.
- risk 0.34cvss —epss 0.00
Our 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…
- risk 0.34cvss —epss 0.00
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 multiple valid …
- risk 0.34cvss —epss 0.00
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 multiple valid …
- risk 0.33cvss —epss 0.00
When 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…
- risk 0.33cvss 6.1epss 0.00
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 formatting, this…
- risk 0.32cvss —epss 0.00
When 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…
- risk 0.31cvss 5.9epss 0.00
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: * It was…
- risk 0.28cvss 5.4epss 0.00
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, making exploitation…
- risk 0.28cvss 5.3epss 0.01
An issue was discovered in pretix before 2023.7.1. Incorrect parsing of configuration files causes the application to trust unchecked X-Forwarded-For headers even though it has not been configured to do so. This can lead to IP address spoofing by users of the application.
Page 1 of 3