Insufficient validation of payment status in pretix-girosolution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pretix GmbH | pretix-girosolution | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pretix Gmbh | Pretix-girosolution |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.331% probability within 30 days)
| Link | Providers |
|---|---|
| https://pretix.eu/about/en/blog/20260728-release-2026-6-1/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pretix Gmbh
Pretix Gmbh pretix-girosolution |
|
| Vendors & Products |
Pretix Gmbh
Pretix Gmbh pretix-girosolution |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 one payment. | |
| Title | Insufficient validation of payment status in pretix-girosolution | |
| Weaknesses | CWE-841 | |
| References |
| |
| Metrics |
cvssV4_0
|