Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-68500 high CVSS 7.5

Vulnerability in sylius/mollie-plugin (CVE-2026-68500)

Summary

Vulnerability in sylius/mollie-plugin (CVE-2026-68500). Data can be tampered with by attackers. Exploitable via POST /{_locale}/update-payment. Mitigation: upgrade to 3.3.1 or later.

Original description

The description as published by the source.

Impact

The shop payment webhook POST /{_locale}/update-payment (route
sylius_mollie_shop_payment_webhook) accepts two independent, attacker-controlled
parameters: id (the Mollie payment ID, verified against Mollie's API) and orderId (the
Sylius order ID, read directly from the database). The handler never verifies that the
Mollie payment belongs to the referenced order.

An unauthenticated attacker who holds any valid paid Mollie payment ID, for example
from a EUR 1 order they placed themselves, can submit it together with any victim
orderId. The victim's order payment is then transitioned to completed (or any other
Mollie-derived state) without any funds being transferred for that order. Sylius order IDs
are sequential integers, and the endpoint requires no authentication, CSRF token or rate
limiting, so the attack scales trivially across all pending orders.

Patches

Fixed in versions 2.2.8, 3.2.4 and 3.3.1. The webhook now binds the payment to
the order: it reads the Mollie payment ID stored server-side for that order when the payment
was created and compares it to the incoming Mollie payment ID. On mismatch the request is
acknowledged with HTTP 200 and no state change is applied. HTTP 200 is intentional,
because Mollie retries the webhook on any non-2xx response.

The stored ID lives in one of two places depending on the checkout flow, and the fix reads
both of them (mirroring CaptureAction):…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-68500 has been found in sylius/mollie-plugin.
Attackers can target a specific entry point like POST /{_locale}/update-payment over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.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-68500" on the vendor's site.

CVE-2026-68500 (sylius/mollie-plugin) — CWE-639 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /{_locale}/update-payment / sylius_mollie_shop_payment_webhook / orderId / completed
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 POST /{_locale}/update-payment without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of sylius/mollie-plugin. Attack surface: POST /{_locale}/update-payment / sylius_mollie_shop_payment_webhook / orderId / completed.

🔥 Severity

Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.

🔧 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 POST /{_locale}/update-payment 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'sylius/mollie-plugin' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で sylius/mollie-plugin を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /{_locale}/update-payment' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /{_locale}/update-payment への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade sylius/mollie-plugin to 3.3.1

    ステージング環境で 3.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /{_locale}/update-payment on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer sylius/mollie-plugin
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.1"}]}]
Packagist sylius/mollie-plugin
[{"type":"ECOSYSTEM","events":[{"introduced":"3.3.0"},{"fixed":"3.3.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details