Search vulnerabilities

Results 46

Export CSV
CVE-2026-131170

Insufficient validation of payment status for Stripe

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 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.

CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131169

Permissions are copied when copying scheduled exports

When 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.

CVSS 4.0 · 2.1 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131168

Validation bypass allows buying sold-out products

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.

CVSS 4.0 · 6.6 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131167

Unsafe usage of return values

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 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.

CVSS 4.0 · 8.9 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131166

Incorrect device security profile

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 intended. If the device is in kiosk mode, the search button will still be hidden from users.

CVSS 4.0 · 6 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131164

Link to parent order or ticket exposed in certain conditions

When 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.

CVSS 4.0 · 2.3 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131165

Incorrect check of permissions in scheduled exports

The 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.

CVSS 4.0 · 2.1 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-131163

Stored XSS in pretix-adyen

A 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.

CVSS 4.0 · 8.6 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-101275

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 with only one payment.

CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-127138

Circumvention of offline barcode revocation check in pretixSCAN

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 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.

CVSS 4.0 · 6.8 Medium EPSS < 1% KEV · Not listed
Vendors
CVE-2026-127139

Insecure device token generation in pretixSCAN Proxy

pretixSCAN 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.

CVSS 4.0 · 4.4 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-127140

Server-Side Request Forgery in pretix Widget WordPress plugin

Our 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.

CVSS 4.0 · 3.8 Low EPSS < 1% KEV · Not listed
CVE-2026-127174

Permission bypass through editing scheduled exports

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 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.

CVSS 4.0 · 5.1 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-125744

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.

CVSS 4.0 · 1.2 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-101272

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 creating the fix. Since the files are referred to by randomly generated UUIDs and only exist for a day, there is virtually no risk, but it renders the added protection mechanism useless. As part of the fix, we have also improved hardening of some other related code areas.

CVSS 4.0 · 2.3 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-101273

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 secret. The gift card is not charged in this case, but by then triggering a refund on the payment, one can increase the value of the gift card.

CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-101274

Improper Validation of response_type Enables Unauthorized Token Issuance in pretix SSO

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 client was configured to only allow the `code` response type, which requires knowledge of the client secret to use and would wrongfully send a response type like `id_token`, it would receive back a valid token. Exploiting this requires the attacker to run JavaScript on the page specified by `redirect_uri`, which must be from a list specified in the client configuration.

CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-101266

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.

CVSS 4.0 · 1.3 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-101267

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.

CVSS 4.0 · 2.7 Low EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2026-101268

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 attack only works when the event is available on a different domain than the organizer page.

CVSS 4.0 · 1.7 Low EPSS < 1% KEV · Not listed
Vendors
Products