Ticket payment bypass via replayed status response
Published Jun 25, 2026 · Updated Jun 25, 2026
Payment workflow bypass in pretix GmbH pretix-computop before 1.3.2 allows remote attackers to obtain multiple valid tickets for one payment. Payment-status processing accepts a response issued for one payment when it is supplied for a different payment, rather than correlating it with the payment being completed. The attacker must first obtain a legitimate successful response and replay it for another payment; the bounded result is extra valid tickets without extra payment.
Summary
What happened
Payment workflow bypass in pretix GmbH pretix-computop before 1.3.2 allows remote attackers to obtain multiple valid tickets for one payment. Payment-status processing accepts a response issued for one payment when it is supplied for a different payment, rather than correlating it with the payment being completed. The attacker must first obtain a legitimate successful response and replay it for another payment; the bounded result is extra valid tickets without extra payment.
The record
- CVE
- CVE-2026-13223
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- pretix GmbH
- Product
- pretix-computop
- Classifications
- CWE-841, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo