Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
11 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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 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.
Recommended action: Upgrade to 2026.4.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 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, "errorreason": null, "errorexplanation": null, "position": 321, "datetime": "2020-08-23T09:00:00+02:00", "list": 456, "created": "2020-08-23T09:00:00+02:00", "autocheckedin": false, "gate": null, "device": 1, "deviceid": 1, "type": "entry" } An unauthorized user usually has no way to match these IDs (position) back to individual people.
Recommended action: Upgrade to 2026.3.1, 2026.2.1 or 2026.1.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 possible to exfiltrate information about the pretix system through specially crafted placeholder names such as {event.init.code.cofilename}}. This way, an attacker with the ability to control email templates (usually every user of the pretix backend) could retrieve sensitive information from the system configuration, including even database passwords or API keys. pretix does include mechanisms to prevent the usage of such malicious placeholders, however due to a mistake in the code, they were not fully effective for the email subject. - Placeholders in subjects and plain text bodies of emails were wrongfully evaluated twice. Therefore, if the first evaluation of a placeholder again contains a placeholder, this second…
Recommended action: Upgrade to 2026.1.1, 2025.10.2 or 2025.9.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.
Recommended action: Upgrade to 2025.10.1, 2025.9.3 or 2025.8.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.
Recommended action: Upgrade to 2025.10.1, 2025.9.3 or 2025.8.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 was rendered as HTML in the resulting email. This way, a user could inject links or other formatted text through a maliciously formatted name. Since pretix applies a strict allow list approach to allowed HTML tags, this could not be abused for XSS or similarly dangerous attack chains. However, it can be used to manipulate emails in a way that makes user-provided content appear in a trustworthy and credible way, which can be abused for phishing.
Recommended action: Upgrade to 2025.9.2, 2025.8.2 or 2025.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 unlikely. However, combined with a CSP bypass (which is not currently known) the vulnerability could be used to impersonate other organizers or staff users.
Recommended action: Upgrade to 2024.7.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
pretix before 2024.1.1 mishandles file validation.
Recommended action: Upgrade to 2024.1.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.
Recommended action: Upgrade to 2023.7.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
pretix before 2023.7.2 allows Pillow to parse EPS files.
Recommended action: Upgrade to 2023.7.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
rami.io pretix before 4.17.1 allows OAuth application authorization from a logged-out session. The fixed versions are 4.15.1, 4.16.1, and 4.17.1.
Recommended action: Upgrade to 4.17.1, 4.16.1 or 4.15.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.