CVE-2026-13222: pretix-oppwa improper validation of payment status

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

A vulnerability in the Oppwa payment integration 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 can 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-13222 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-13222 being exploited in the wild.
How severe is CVE-2026-13222?
Informational severity, with a CVSS score of 6.3, published 25 June 2026.
Which products and versions are affected?
Pretix-Oppwa < 1.4.3.
Is there a fix for CVE-2026-13222?
A patch was published on 2026-06-25. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-13222 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-13222?
Check whether you run Pretix-Oppwa 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 pretix-oppwa plugin (the Oppwa-based payment integration for pretix) contains a logic flaw in its payment status validation. The component fails to sufficiently verify that a payment status response corresponds to the specific transaction being processed. An attacker can exploit this by capturing a successful payment status response from one transaction and replaying or supplying it to the system for a different order. This results in the system marking multiple orders as paid based on a single actual payment. The vulnerability is fixed in version 1.4.3.

Affected products

  • pretix pretix-oppwa < 1.4.3

Timeline

  • 2026-06-25: disclosed
  • 2026-06-25: advisory
  • 2026-06-25: patched

References

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