Lucene search
+L

10 matches found

osv_cve
osv_cve
•added 2026/10/23 9:50 p.m.•12 views

CVE-2026-115937 Unauthenticated payment reuse allows unpaid orders to be marked as paid

The Mollie webhook endpoint accepts two independent, attacker-controlled parameters and never verifies that they belong together: commerceTransactionHash — selects which Craft Commerce transaction is completed id — selects which Mollie payment is queried for its status An unauthenticated attacker...

8.7CVSS5.9AI score
SaveExploits0References7
Cvelist
Cvelist
•added 2026/10/23 9:50 p.m.•23 views

CVE-2026-115937 Unauthenticated payment reuse allows unpaid orders to be marked as paid

The Mollie webhook endpoint accepts two independent, attacker-controlled parameters and never verifies that they belong together: commerceTransactionHash — selects which Craft Commerce transaction is completed id — selects which Mollie payment is queried for its status An unauthenticated attacker...

8.7CVSS0.00166EPSS
SaveExploits0References4
CVE
CVE
•added 2026/10/23 9:50 p.m.•13 views

CVE-2026-115937

The Mollie webhook endpoint in Craft Commerce is vulnerable to an unauthenticated payment reuse flaw due to insufficient verification of data authenticity (CWE-345). The application fails to verify that the commerceTransactionHash and id parameters belong together. An unauthenticated attacker pos...

8.7CVSS5.9AI score0.00166EPSS
SaveExploits0References4
CVE
CVE
•added 2026/07/28 10:39 a.m.•49 views

CVE-2026-18029

The CVE-2026-18029 entry is tied to the pretix-girosolution payment integration. Affected component: payment status validation in GiroCheckout flow. Root cause: insufficient validation of payment status responses, enabling an attacker to reuse a successful status for one payment with a different ...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/06/25 2:08 p.m.•36 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
Vulnrichment
Vulnrichment
•added 2026/06/25 2:08 p.m.•22 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
Cvelist
Cvelist
•added 2026/06/25 2:07 p.m.•61 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
CVE
CVE
•added 2026/06/25 2:03 p.m.•49 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.•56 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
Positive Technologies
Positive Technologies
•added 2026/06/25 12:00 a.m.•36 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.8AI score0.00331EPSS
SaveExploits0References2
Rows per page
Query Builder