VYPR

Vendor CVEs

Pretix

All CVEs

49 total · sorted by risk
  • CVE-2024-27447CriFeb 26, 2024
    risk 0.64cvss 9.8epss 0.01

    pretix before 2024.1.1 mishandles file validation.

  • CVE-2026-131167HigNov 20, 2026
    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…

  • CVE-2026-131163HigNov 20, 2026
    risk 0.56cvss —epss 0.01

    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…

  • CVE-2026-13603CriJul 1, 2026
    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…

  • CVE-2026-127138MedNov 17, 2026
    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…

  • CVE-2023-44464HigSep 29, 2023
    risk 0.44cvss 7.8epss 0.00

    pretix before 2023.7.2 allows Pillow to parse EPS files.

  • CVE-2026-13602HigJul 1, 2026
    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,…

  • CVE-2026-2452MedFeb 16, 2026
    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…

  • CVE-2026-2451MedFeb 16, 2026
    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…

  • CVE-2026-101275MedNov 10, 2026
    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.

  • CVE-2026-101274MedOct 28, 2026
    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…

  • CVE-2026-131168MedNov 20, 2026
    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.

  • CVE-2026-131170MedNov 20, 2026
    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…

  • CVE-2026-13223MedJun 25, 2026
    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 …

  • CVE-2026-13222MedJun 25, 2026
    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 …

  • CVE-2026-127174MedNov 17, 2026
    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…

  • CVE-2025-13742MedNov 27, 2025
    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…

  • CVE-2026-131166MedNov 20, 2026
    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…

  • CVE-2026-2415MedFeb 16, 2026
    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…

  • CVE-2026-127139MedNov 17, 2026
    risk 0.29cvss —epss 0.00

    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…

  • CVE-2024-8113MedAug 23, 2024
    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…

  • CVE-2023-44463MedOct 2, 2023
    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.

  • CVE-2026-101273MedOct 28, 2026
    risk 0.27cvss —epss 0.00

    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…

  • CVE-2026-13225MedJun 25, 2026
    risk 0.27cvss —epss 0.00

    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.

  • CVE-2026-127140LowNov 17, 2026
    risk 0.25cvss —epss 0.00

    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…

  • CVE-2026-5600MedApr 8, 2026
    risk 0.21cvss 4.3epss 0.00

    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 …

  • CVE-2026-9712LowMay 27, 2026
    risk 0.18cvss —epss 0.00

    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…

  • CVE-2025-14882LowDec 19, 2025
    risk 0.18cvss —epss 0.00

    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.

  • CVE-2025-14881LowDec 19, 2025
    risk 0.18cvss —epss 0.00

    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.

  • CVE-2026-11764LowJun 9, 2026
    risk 0.16cvss —epss 0.00

    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 letters of the gift…

  • CVE-2026-101267LowSep 29, 2026
    risk 0.11cvss —epss 0.00

    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.

  • CVE-2026-131164LowNov 20, 2026
    risk 0.08cvss —epss 0.01

    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…

  • CVE-2026-101272LowOct 28, 2026
    risk 0.08cvss —epss 0.00

    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…

  • CVE-2026-101269LowSep 29, 2026
    risk 0.08cvss —epss 0.00

    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 a day, there is…

  • CVE-2026-131169LowNov 20, 2026
    risk 0.07cvss —epss 0.01

    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.

  • CVE-2026-131165LowNov 20, 2026
    risk 0.07cvss —epss 0.01

    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…

  • CVE-2026-101271LowSep 29, 2026
    risk 0.07cvss —epss 0.00

    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.

  • CVE-2026-101270LowSep 29, 2026
    risk 0.07cvss —epss 0.00

    Malicious HTML content could be injected into the help texts of various fields with organizer permissions.

  • CVE-2026-101268LowSep 29, 2026
    risk 0.04cvss —epss 0.00

    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…

  • CVE-2026-125744LowNov 10, 2026
    risk 0.01cvss —epss 0.00

    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.

  • CVE-2026-101266LowSep 29, 2026
    risk 0.01cvss —epss 0.00

    A logic flaw in the checkout flow allows users to bypass validations performed during the check-in by skipping entire check-in steps.

  • CVE-2026-18029MedJul 28, 2026
    risk 0.00cvss —epss 0.00

    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 tickets with only …

  • CVE-2026-18028LowJul 28, 2026
    risk 0.00cvss —epss 0.00

    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 attacker could…

  • CVE-2026-57536MedJun 25, 2026
    risk 0.00cvss —epss 0.00

    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 with only one…

  • CVE-2026-57535LowJun 25, 2026
    risk 0.00cvss —epss 0.00

    Content injected to PDF rendering contexts could, in many places, include HTML content including tags. If the src attribute of these images pointed to an URL, the PDF rendering engine would download the image from that place and display it, thereby leaking information…

  • CVE-2026-57534LowJun 25, 2026
    risk 0.00cvss —epss 0.00

    Malicious HTML content could be injected into the content of a page in the pretix-pages plugin.

  • CVE-2026-57533LowJun 25, 2026
    risk 0.00cvss —epss 0.00

    Malicious HTML content could be injected into the page pretix shows when redirection to an untrusted page occurs. Since this page has a Content-Security-Policy, this can mainly be used for phishing purposes.

  • CVE-2026-57532HigJun 25, 2026
    risk 0.00cvss —epss 0.00

    Malicious HTML content contained in the layout specification of a PDF ticket or badge layout was executed when the PDF editor is opened in the browser. This could allow one backend user to inject JavaScript into the browser context of another backend user. Due to requirements…

  • CVE-2026-13314LowJun 25, 2026
    risk 0.00cvss —epss 0.00

    Malicious HTML content could be injected into the content rendered by the pretix-digital plugin.