Unauthenticated payment reuse allows unpaid orders to be marked as paid
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.4.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Mollie payment gateway integration for Craft Commerce, a commerce plugin for the Craft CMS, is affected. An unauthenticated attacker can pair a valid paid Mollie payment ID with a different order's transaction, causing unpaid orders to be marked as fully paid.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- craftcms/commerce-mollie
From 2.1.1 · fixed in 4.4.3