Lucene search
+L

30 matches found

NVD
NVD
•added 2026/11/10 12:17 p.m.•9 views

CVE-2026-101275

Our payment integration with Adyen 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.00207EPSS
SaveExploits0References1
osv_cve
osv_cve
•added 2026/11/10 12:00 p.m.•11 views

CVE-2026-101275 Insufficient validation of payment status in pretix-adyen

Our payment integration with Adyen 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
CVE
CVE
•added 2026/11/10 12:00 p.m.•13 views

CVE-2026-101275

The pretix-adyen payment integration contains a vulnerability due to insufficient validation of payment status responses from Adyen. An attacker can exploit this by reusing a successful payment status response from a single transaction to authorize multiple different payments, potentially gaining...

6.3CVSS6AI score0.00207EPSS
SaveExploits0References1
Mend
Mend
•added 2026/11/10 12:00 p.m.•5 views

CVE-2026-101275

Our payment integration with Adyen 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 score0.00207EPSS
SaveExploits0References5
Cvelist
Cvelist
•added 2026/11/10 12:00 p.m.•40 views

CVE-2026-101275 Insufficient validation of payment status in pretix-adyen

Our payment integration with Adyen 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.00207EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/11/10 12:00 p.m.•2 views

CVE-2026-101275 Insufficient validation of payment status in pretix-adyen

Our payment integration with Adyen 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 score0.00207EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/11/10 12:00 p.m.•8 views

EUVD-2026-120896

Our payment integration with Adyen 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 score0.00207EPSS
SaveExploits0References1
Positive Technologies
Positive Technologies
•added 2026/11/10 12:00 a.m.•5 views

PT-2026-141587

Our payment integration with Adyen 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.3CVSS6.1AI score0.00207EPSS
SaveExploits0References2
NVD
NVD
•added 2026/07/28 11:17 a.m.•28 views

CVE-2026-18029

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...

6.3CVSS0.00331EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/07/28 10:39 a.m.•27 views

CVE-2026-18029 Insufficient validation of payment status in pretix-girosolution

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...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/07/28 10:39 a.m.•33 views

EUVD-2026-49752

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...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2026/07/28 12:00 a.m.•22 views

CVE-2026-18029: Improper Enforcement of Behavioral Workflow

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...

6.3CVSS5.8AI score0.00331EPSS
SaveExploits0References2
NVD
NVD
•added 2026/06/25 3:16 p.m.•44 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.3CVSS0.00331EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/06/25 2:08 p.m.•42 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.3CVSS6AI score0.00331EPSS
SaveExploits0References1
osv_cve
osv_cve
•added 2026/06/25 2:08 p.m.•32 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 score0.00331EPSS
SaveExploits0References5
CVE
CVE
•added 2026/06/25 2:08 p.m.•77 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.3CVSS6AI score0.00331EPSS
SaveExploits0References1
attackerkb
attackerkb
•added 2026/06/25 2:08 p.m.•25 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.3CVSS6.1AI score0.00331EPSS
SaveExploits0References2
Vulnrichment
Vulnrichment
•added 2026/06/25 2:07 p.m.•26 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.9AI score0.00331EPSS
SaveExploits0References1
osv_cve
osv_cve
•added 2026/06/25 2:07 p.m.•27 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.9AI score0.00331EPSS
SaveExploits0References5
EUVD
EUVD
•added 2026/06/25 2:07 p.m.•34 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.9AI score0.00331EPSS
SaveExploits0References1
Rows per page
Query Builder