CVE-2026-13223: pretix pretix-computop improper payment status validation

CVE-2026-13223 · Severity: info · CVSS 6.3 · Published 2026-06-25

A vulnerability in the Computop payment plugin for the pretix ticketing system allows users to bypass payment requirements. By reusing a valid payment confirmation from one transaction for a different order, an attacker could obtain multiple tickets while only paying for one. This could lead to financial loss for event organizers and unauthorized access to events.

Vendors: Pretix.

Quick answers

Is CVE-2026-13223 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-13223 being exploited in the wild.
How severe is CVE-2026-13223?
Informational severity, with a CVSS score of 6.3, published 25 June 2026.
Which products and versions are affected?
Pretix-Computop < 1.3.2.
Is there a fix for CVE-2026-13223?
A patch was published on 2026-06-25: Fixed in version 1.3.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-13223 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-13223?
Check whether you run Pretix-Computop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is classified as an improper enforcement of behavioral workflow (CWE-841) within the pretix-computop payment integration. The root cause is a failure to uniquely bind a payment status response from the Computop gateway to a specific transaction. An attacker can intercept or obtain a successful payment status response and replay it to the system for a different order. This allows for the generation of valid tickets without corresponding payments. The issue is fixed in version 1.3.2 of the pretix-computop plugin.

Affected products

  • pretix pretix-computop < 1.3.2

Timeline

  • 2026-06-25: disclosed
  • 2026-06-25: patched: Fixed in version 1.3.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.