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


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-3qcx-mjf6-48vj, GHSA-8pqg-7g86-mxqf

## What is CVE-2026-115937?

CVE-2026-115937 is a high-severity vulnerability in craftcms commerce-mollie, published on 23 Oct 2026. 

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

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-115937?


## How do I fix CVE-2026-115937?

No fix has been published for CVE-2026-115937 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115937 being exploited?

There is no known exploitation of CVE-2026-115937 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115937 and fix it if it is affected.

What it is: CVE-2026-115937 is a high-severity vulnerability in craftcms commerce-mollie, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115937 in the wild and no public exploit code.

Affected product: craftcms commerce-mollie. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115937/ (Markdown: https://insights.sbomify.com/CVE-2026-115937/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115937
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115937
- OSV: https://osv.dev/vulnerability/CVE-2026-115937

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115937/
Summaries are generated and may contain mistakes; the official description above is the record.