← Back
CVE-2026-68501
medium
CVSS 6.5
Vulnerability in sylius/mollie-plugin (CVE-2026-68501)
Summary
vulnerability in sylius/mollie-plugin (CVE-2026-68501). Risk of unauthorized operations or information disclosure. Exploitable via `GET /{_locale}/thank-you`. Mitigation: upgrade to `3.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-68501** has been found in sylius/mollie-plugin.
Attackers can target a specific entry point like `GET /{_locale}/thank-you` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade sylius/mollie-plugin to **3.3.1** or later.
If unsure, ask your IT team or search "sylius/mollie-plugin CVE-2026-68501" on the vendor's site.
CVE-2026-68501 (sylius/mollie-plugin) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /{_locale}/thank-you / GET /{_locale}/get-code / GET /{_locale}/register-after-checkout/{tokenValue} / `orderId`
Patched: `3.3.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-639) exists in sylius/mollie-plugin. Attackers reach the vulnerable code path via `GET /{_locale}/thank-you` without authentication.
📍 Affected scope
sylius/mollie-plugin — . Attack surface: GET /{_locale}/thank-you / GET /{_locale}/get-code / GET /{_locale}/register-after-checkout/{tokenValue} / `orderId`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.3.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /{_locale}/thank-you` requests with malformed payloads or SQL meta-characters. Run `grep -r 'sylius/mollie-plugin' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sylius/mollie-plugin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sylius/mollie-plugin` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /{_locale}/thank-you' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /{_locale}/thank-you` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade sylius/mollie-plugin to 3.3.1ステージング環境で 3.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /{_locale}/thank-you on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
sylius/mollie-plugin
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.1"}]}]
References
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://nvd.nist.gov/vuln/detail/CVE-2026-68501
- web https://github.com/advisories/GHSA-x83g-979r-f5fh