# CVE-2026-68501: Sylius Mollie Plugin: Unauthenticated IDOR leaks order token and customer PII

> Unauthenticated attackers can enumerate order IDs to leak tokens and access customer PII via Sylius Mollie plugin endpoints.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-x83g-979r-f5fh

## What is CVE-2026-68501?

CVE-2026-68501 is a medium-severity missing authorization vulnerability in Sylius MolliePlugin, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sylius Mollie Plugin provides Mollie payment integration for Sylius applications. Prior to 2.2.8, 3.2.4, and 3.3.1, Sylius Mollie Plugin's GET /{_locale}/thank-you PageRedirectController::thankYouAction and GET /{_locale}/get-code QrCodeAction::fetchQrCodeFromOrder endpoints look up sequential orderId values without ownership or session checks, exposing order tokenValue values that can be used with GET /{_locale}/register-after-checkout/{tokenValue} to view customer first name, last name, and email. This issue is fixed in 2.2.8, 3.2.4, and 3.3.1.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

6 open source packages ship an affected version, including sylius/mollie-plugin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sylius/mollie-plugin` | Packagist | All versions | 2.2.8 |
| `sylius/mollie-plugin` | Packagist | All versions | 2.2.8 |
| `sylius/mollie-plugin` | Packagist | From 3.0.0 | 3.2.4 |
| `sylius/mollie-plugin` | Packagist | From 3.0.0 | 3.2.4 |
| `sylius/mollie-plugin` | Packagist | From 3.3.0 | 3.3.1 |
| `sylius/mollie-plugin` | Packagist | From 3.3.0 | 3.3.1 |

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

Upgrade sylius/mollie-plugin to a fixed version for your release line: 2.2.8, 3.2.4 or 3.3.1.

## Is CVE-2026-68501 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68501 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68501 is a medium-severity missing authorization vulnerability in Sylius MolliePlugin, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68501 exists.

Affected packages and fixed versions:
- sylius/mollie-plugin (Packagist): affected all versions; fixed in 2.2.8
- sylius/mollie-plugin (Packagist): affected all versions; fixed in 2.2.8
- sylius/mollie-plugin (Packagist): affected from 3.0.0; fixed in 3.2.4
- sylius/mollie-plugin (Packagist): affected from 3.0.0; fixed in 3.2.4
- sylius/mollie-plugin (Packagist): affected from 3.3.0; fixed in 3.3.1
- sylius/mollie-plugin (Packagist): affected from 3.3.0; fixed in 3.3.1

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-68501/ (Markdown: https://insights.sbomify.com/CVE-2026-68501/index.md)
```

## Sources

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

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