Lucene search
+L

26987 matches found

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

CVE-2026-13222

Our payment integration with Oppwa-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
NVD
NVD
•added 2026/06/25 3:16 p.m.•28 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
CVE
CVE
•added 2026/06/25 2:08 p.m.•67 views

CVE-2026-57536

CVE-2026-57536 affects the pretix-mollie payment integration, where payment status responses are not properly validated. An attacker could reuse a successful payment status from one payment and apply it to a different payment, potentially gaining access to multiple valid tickets with a single pay...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Cvelist
Cvelist
•added 2026/06/25 2:08 p.m.•55 views

CVE-2026-57536 Insufficient validation of payment status in pretix-mollie

Our payment integration with Mollie 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...

6.3CVSS0.00331EPSS
SaveExploits0References1
attackerkb
attackerkb
•added 2026/06/25 2:08 p.m.•21 views

CVE-2026-57536

Our payment integration with Mollie 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...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References2
Vulnrichment
Vulnrichment
•added 2026/06/25 2:08 p.m.•21 views

CVE-2026-57536 Insufficient validation of payment status in pretix-mollie

Our payment integration with Mollie 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...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/06/25 2:08 p.m.•35 views

EUVD-2026-39415

Our payment integration with Mollie 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...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
osv_cve
osv_cve
•added 2026/06/25 2:08 p.m.•21 views

CVE-2026-57536 Insufficient validation of payment status in pretix-mollie

Our payment integration with Mollie 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...

6.3CVSS6AI score
SaveExploits0References5
Cvelist
Cvelist
•added 2026/06/25 2:07 p.m.•58 views

CVE-2026-13222 Insufficient validation of payment status in pretix-oppwa

Our payment integration with Oppwa-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_cve
osv_cve
•added 2026/06/25 2:07 p.m.•19 views

CVE-2026-13222 Insufficient validation of payment status in pretix-oppwa

Our payment integration with Oppwa-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
SaveExploits0References5
Mend
Mend
•added 2026/06/25 2:07 p.m.•6 views

CVE-2026-13222

Our payment integration with Oppwa-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
SaveExploits0References5
EUVD
EUVD
•added 2026/06/25 2:07 p.m.•29 views

EUVD-2026-39414

Our payment integration with Oppwa-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:07 p.m.•49 views

CVE-2026-13222

The CVE-2026-13222 entry concerns the pretix-oppwa payment integration, where insufficient validation of payment status responses allows reusing a valid payment status across different payments. This could enable an attacker to gain access to multiple valid tickets tied to a single payment. Affec...

6.3CVSS5.8AI score0.00331EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/06/25 2:07 p.m.•23 views

CVE-2026-13222 Insufficient validation of payment status in pretix-oppwa

Our payment integration with Oppwa-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
Vulnrichment
Vulnrichment
•added 2026/06/25 2:03 p.m.•19 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
Cvelist
Cvelist
•added 2026/06/25 2:03 p.m.•52 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
EUVD
EUVD
•added 2026/06/25 2:03 p.m.•24 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.8AI score0.00331EPSS
SaveExploits0References1
CVE
CVE
•added 2026/06/25 2:03 p.m.•47 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
osv_cve
osv_cve
•added 2026/06/25 2:03 p.m.•17 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
Circl
Circl
•added 2026/06/25 10:16 a.m.•26 views

CVE-2026-52943

creationtimestamp| type| source ---|---|--- 2026-06-25 10:16:35+00:00| seen| https://infosec.exchange/users/vuldb/statuses/116810225692140650 2026-07-01 02:47:28+00:00| seen| https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0812 2026-07-06 06:45:02+00:00| seen|...

7.8CVSS7.3AI score0.00247EPSS
SaveExploits1References5
Rows per page
Query Builder