CVE-2026-115937

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 holding any paid Mollie payment ID from the merchant’s account can pair it with any transaction hash.

Commerce queries Mollie, sees status: paid, and marks the target transaction successful for that transaction’s full amount, regardless of how much was actually 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 holding any paid Mollie payment ID from the merchant’s account can pair it with any transaction hash.

Commerce queries Mollie, sees status: paid, and marks the target transaction successful for that transaction’s full amount, regardless of how much was actually 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 holding any paid Mollie payment ID from the merchant’s account can pair it with any transaction hash.

Commerce queries Mollie, sees status: paid, and marks the target transaction successful for that transaction’s full amount, regardless of how much was actually 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 holding any paid Mollie payment ID from the merchant’s account can pair it with any transaction hash.

Commerce queries Mollie, sees status: paid, and marks the target transaction successful for that transaction’s full amount, regardless of how much was actually 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 holding any paid Mollie payment ID from the merchant’s account can pair it with any transaction hash.

Commerce queries Mollie, sees status: paid, and marks the target transaction successful for that transaction’s full amount, regardless of how much was actually paid.