Lucene search
+L

8 matches found

NVD
NVD
•added 2026/06/25 3:16 p.m.•25 views

CVE-2026-13223

Our payment integration with Computop-based payment methods 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...

6.3CVSS0.00331EPSS
SaveExploits0References1
OSV
OSV
•added 2026/06/25 2:03 p.m.•13 views

CVE-2026-13223 Insufficient validation of payment status in pretix-computop

Our payment integration with Computop-based payment methods 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...

6.3CVSS6AI score
SaveExploits0References5
EUVD
EUVD
•added 2026/06/25 2:03 p.m.•20 views

EUVD-2026-39413

Our payment integration with Computop-based payment methods 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...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/06/25 2:03 p.m.•14 views

CVE-2026-13223 Insufficient validation of payment status in pretix-computop

Our payment integration with Computop-based payment methods 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...

6.3CVSS5.8AI score0.00331EPSS
SaveExploits0References1
CVE
CVE
•added 2026/06/25 2:03 p.m.•42 views

CVE-2026-13223

Affected component: pretix with Computop-based payment methods. Root cause: insufficient validation of payment status responses. Impact: an attacker could reuse a successful status for one payment to complete a different payment, gaining access to multiple valid tickets from a single payment. Thi...

6.3CVSS5.8AI score0.00331EPSS
SaveExploits0References1
Cvelist
Cvelist
•added 2026/06/25 2:03 p.m.•49 views

CVE-2026-13223 Insufficient validation of payment status in pretix-computop

Our payment integration with Computop-based payment methods 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...

6.3CVSS0.00331EPSS
SaveExploits0References1
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2026/06/25 12:00 a.m.•6 views

CVE-2026-13223: Improper Enforcement of Behavioral Workflow

Our payment integration with Computop-based payment methods 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...

6.3CVSS5.7AI score0.00331EPSS
SaveExploits0References2
Positive Technologies
Positive Technologies
•added 2026/06/25 12:00 a.m.•28 views

PT-2026-52441

Our payment integration with Computop-based payment methods 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...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References2
Rows per page
Query Builder