VYPR

Pretix

by Pretix

pypi: pretix

Source repositories

CVEs (46)

  • 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-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…