Read the docs

Unauthenticated payment reuse marks unpaid Craft Commerce orders paid

Priority MEDIUM 43CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-345.

Summary

The Mollie webhook endpoint in the craftcms commerce-mollie plugin, from 2.1.1 before 4.4.3, accepts two independent attacker-controlled parameters and never checks that they belong together. An unauthenticated attacker who holds any paid Mollie payment ID from the merchant's account can pair it with any Craft Commerce transaction hash, causing that transaction to be marked successful for its full amount regardless of the amount paid. This is an insufficient verification of data authenticity (CWE-345).

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00166 5th percentileScored 2026-11-07
Fix Fixed commerce-mollie (craftcms): 4.4.3

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Craft CMScommerce-mollie2.1.1 to before 4.4.34.4.3Patch availableCNA
  • commerce-mollie VendorCraft CMS Affected 2.1.1 to before 4.4.3 Fixed in 4.4.3 Patch available CNA

Remediation

Upgrade craftcms commerce-mollie to version 4.4.3 or later, which is the fixed version listed for this package.

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

  • Fix · CNA commerce-mollie (craftcms) Fixed in 4.4.3

Timeline

  1. 2026-10-23 Threatist record created from CVE-2026-115937
  2. 2026-10-24 Alias added: GHSA-8pqg-7g86-mxqf
  3. 2026-10-24 Priority changed: MEDIUM → LOW
  4. 2026-11-02 CISA SSVC decision points changed
  5. 2026-11-02 Priority changed: LOW → MEDIUM

References

  • TI-2025-23503 Craft CMS Allows Remote Code Execution KEVCVSS 3.1CRITICAL 10.0
  • TI-2024-37138 RCE when PHP `register_argc_argv` config setting is enabled in craftcms/cms KEVCVSS 4.0CRITICAL 9.3
  • TI-2025-16994 Potential RCE with a compromised security key in craft/cms KEVCVSS 3.1HIGH 8.1
  • TI-2025-24595 Craft CMS stores user-provided content in session files KEVCVSS 4.0MEDIUM 6.9
  • TI-2023-22284 Craft CMS Remote Code Execution vulnerability CVSS 3.1CRITICAL 10.0
  • TI-2024-25171 Craft CMS up to v3.7.31 was discovered to contain a SQL injection vulnerability via the GraphQL API endpoint. CVSS 3.1CRITICAL 9.8
See all 203 →

Sources