CVE-2026-68500: Sylius/mollie plugin Sylius Mollie Plugin Vulnerable To Vulnerability

HIGH
Advisory Identifier: GHSA-rc52-c4hv-w89p
CVSS 7.5
CWE-639
Published
Advisory Summary

CVE-2026-68500 is a HIGH (CVSS 7.5) sylius mollie plugin vulnerable to vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Sylius/mollie plugin libraries in the Packagist ecosystem. The issue involves sylius mollie plugin vulnerable to payment status forgery via the payment webhook. Remediation is available by upgrading affected packages to version 2.2.8, 3.2.4, 3.3.1.

CVE-2026-68500 at a Glance

CVE Identifier CVE-2026-68500
GHSA Identifier GHSA-rc52-c4hv-w89p
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Sylius/mollie plugin
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-68500

To remediate this vulnerability, upgrade all affected Sylius/mollie plugin dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

sylius/mollie-plugin fixed: 2.2.8
Upgrade sylius/mollie-plugin to 2.2.8
sylius/mollie-plugin fixed: 3.2.4
Upgrade sylius/mollie-plugin to 3.2.4
sylius/mollie-plugin fixed: 3.3.1
Upgrade sylius/mollie-plugin to 3.3.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for sylius/mollie-plugin

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-68500, inspect your project dependencies for Sylius/mollie plugin:

inspect dependencies for sylius/mollie-plugin

Analyze the terminal output to locate any version of Sylius/mollie plugin in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.8), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Sylius/mollie plugin, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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`): - `payment.getDetails()['payment_mollie_id']` for the standard Shop API and Apple Pay Direct flows, stored in `CreatePaymentAction`. - `order.getMolliePaymentId()` for the QR-code flow, which stores the ID on the order itself (`QrCodeAction`). Reading only the payment details would reject legitimate QR-code payments, because their payment details carry no `payment_mollie_id`, so both sources must be consulted. ### Workarounds If you cannot upgrade immediately, patch the vulnerability at the project level by decorating the plugin's webhook controller. The decorator checks that the incoming Mollie id matches the id stored for that order **before** handing over to the original controller, so no plugin behaviour (state machine, logging) is lost and no extra Mollie API call is made. Works on both 2.2 and 3.x. #### Step 1. Create the decorator Create `src/Controller/Mollie/SecurePaymentWebhookController.php` in your Sylius project: ```php <?php declare(strict_types=1); namespace App\Controller\Mollie; use Sylius\Component\Core\Model\OrderInterface; use Sylius\Component\Order\Repository\OrderRepositoryInterface; use Sylius\MolliePlugin\Controller\Shop\PaymentWebhookController; use Symfony\Component\HttpFoundation\JsonResponse; use Symfony\Component\HttpFoundation\Request; use Symfony\Component\HttpFoundation\Response; final class SecurePaymentWebhookController { public function __construct( private readonly PaymentWebhookController $inner, private readonly OrderRepositoryInterface $orderRepository, ) { } public function __invoke(Request $request): Response { $orderId = $request->get('orderId'); $molliePaymentId = $request->get('id'); if (null === $orderId || null === $molliePaymentId) { return ($this->inner)($request); } /** @var OrderInterface|null $order */ $order = $this->orderRepository->findOneBy(['id' => $orderId]); if (null === $order) { return ($this->inner)($request); } $storedMollieId = $this->resolveStoredMollieId($order); // Reject any webhook whose Mollie id does not match the one stored for this order. // 200 is intentional: Mollie retries on any non-2xx response. if (null === $storedMollieId || $storedMollieId !== (string) $molliePaymentId) { return new JsonResponse(null, Response::HTTP_OK); } return ($this->inner)($request); } private function resolveStoredMollieId(OrderInterface $order): ?string { $payment = $order->getLastPayment(); $fromDetails = $payment?->getDetails()['payment_mollie_id'] ?? null; if (null !== $fromDetails && '' !== $fromDetails) { return (string) $fromDetails; } // QR-code flow stores the Mollie id on the order itself. if (method_exists($order, 'getMolliePaymentId')) { $fromOrder = $order->getMolliePaymentId(); if (null !== $fromOrder && '' !== $fromOrder) { return (string) $fromOrder; } } return null; } } ``` #### Step 2. Register the decorator Append to your project's `config/services.yaml`: ```yaml services: App\Controller\Mollie\SecurePaymentWebhookController: decorates: sylius_mollie.controller.shop.payment_webhook public: true arguments: $inner: '@.inner' $orderRepository: '@sylius.repository.order' ``` > `decorates:` keeps the original service ID, so the route > `_controller: sylius_mollie.controller.shop.payment_webhook` keeps working with no route > changes. `@.inner` is the original plugin controller. #### Step 3. Clear the cache ```bash bin/console cache:clear ```

CVE-2026-68500 Affected Sylius/mollie plugin Versions

3 component(s)
Fixed Versions:
2.2.83.2.43.3.1
Product / Package Ecosystem Affected Versions Fixed Version
sylius/mollie-plugin
Packagist
< 2.2.8
2.2.8
sylius/mollie-plugin
Packagist
≥ 3.0.0
< 3.2.4
3.2.4
sylius/mollie-plugin
Packagist
≥ 3.3.0
< 3.3.1
3.3.1

References

Frequently Asked Questions

What is CVE-2026-68500?
CVE-2026-68500 is a security vulnerability in Sylius/mollie plugin involving Sylius Mollie Plugin vulnerable to payment status forgery via the payment webhook under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Sylius/mollie plugin versions are affected?
Affected versions include releases prior to 2.2.8, 3.2.4, 3.3.1 across affected packages: sylius/mollie-plugin.
What version fixes CVE-2026-68500?
Upgrading to 2.2.8, 3.2.4, 3.3.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is sylius/mollie-plugin affected?
Yes, sylius/mollie-plugin is affected in releases prior to 2.2.8, 3.2.4, 3.3.1. Upgrade your dependency to 2.2.8, 3.2.4, 3.3.1 or later.
What is the CVSS score of CVE-2026-68500?
CVE-2026-68500 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-68500?
CVE-2026-68500 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Packagist dependencies for CVE-2026-68500?
Run the dependency tree command: 'inspect dependencies for sylius/mollie-plugin'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rc52-c4hv-w89p",
  "modified" : "2026-07-31T16:52:39Z",
  "published" : "2026-07-31T16:52:39Z",
  "aliases" : [ "CVE-2026-68500" ],
  "summary" : "Sylius Mollie Plugin vulnerable to payment status forgery via the payment webhook",
  "details" : "### Impact\n  The shop payment webhook `POST /{_locale}/update-payment` (route\n  `sylius_mollie_shop_payment_webhook`) accepts two independent, attacker-controlled\n  parameters: `id` (the Mollie payment ID, verified against Mollie's API) and `orderId` (the\n  Sylius order ID, read directly from the database). The handler never verifies that the\n  Mollie payment belongs to the referenced order.\n\n  An unauthenticated attacker who holds any valid **paid** Mollie payment ID, for example\n  from a EUR 1 order they placed themselves, can submit it together with any victim\n  `orderId`. The victim's order payment is then transitioned to `completed` (or any other\n  Mollie-derived state) without any funds being transferred for that order. Sylius order IDs\n  are sequential integers, and the endpoint requires no authentication, CSRF token or rate\n  limiting, so the attack scales trivially across all pending orders.\n  \n  ### Patches\n  Fixed in versions **2.2.8**, **3.2.4** and **3.3.1**. The webhook now binds the payment to\n  the order: it reads the Mollie payment ID stored server-side for that order when the payment\n  was created and compares it to the incoming Mollie payment ID. On mismatch the request is\n  acknowledged with `HTTP 200` and no state change is applied. `HTTP 200` is intentional,\n  because Mollie retries the webhook on any non-2xx response.\n\n  The stored ID lives in one of two places depending on the checkout flow, and the fix reads\n  both of them (mirroring `CaptureAction`):\n  \n  - `payment.getDetails()['payment_mollie_id']` for the standard Shop API and Apple Pay Direct\n    flows, stored in `CreatePaymentAction`.\n  - `order.getMolliePaymentId()` for the QR-code flow, which stores the ID on the order itself\n    (`QrCodeAction`).\n\n  Reading only the payment details would reject legitimate QR-code payments, because their\n  payment details carry no `payment_mollie_id`, so both sources must be consulted.\n\n  ### Workarounds\n  If you cannot upgrade immediately, patch the vulnerability at the project level by\n  decorating the plugin's webhook controller. The decorator checks that the incoming Mollie\n  id matches the id stored for that order **before** handing over to the original controller,\n  so no plugin behaviour (state machine, logging) is lost and no extra Mollie API call is\n  made. Works on both 2.2 and 3.x.\n\n  #### Step 1. Create the decorator\n  Create `src/Controller/Mollie/SecurePaymentWebhookController.php` in your Sylius project:\n\n  ```php\n  <?php\n\n  declare(strict_types=1);\n\n  namespace App\\Controller\\Mollie;\n\n  use Sylius\\Component\\Core\\Model\\OrderInterface;\n  use Sylius\\Component\\Order\\Repository\\OrderRepositoryInterface;\n  use Sylius\\MolliePlugin\\Controller\\Shop\\PaymentWebhookController;\n  use Symfony\\Component\\HttpFoundation\\JsonResponse;\n  use Symfony\\Component\\HttpFoundation\\Request;\n  use Symfony\\Component\\HttpFoundation\\Response;\n\n  final class SecurePaymentWebhookController\n  {\n      public function __construct(\n          private readonly PaymentWebhookController $inner,\n          private readonly OrderRepositoryInterface $orderRepository,\n      ) {\n      }\n\n      public function __invoke(Request $request): Response\n      {\n          $orderId = $request->get('orderId');\n          $molliePaymentId = $request->get('id');\n\n          if (null === $orderId || null === $molliePaymentId) {\n              return ($this->inner)($request);\n          }\n\n          /** @var OrderInterface|null $order */\n          $order = $this->orderRepository->findOneBy(['id' => $orderId]);\n          if (null === $order) {\n              return ($this->inner)($request);\n          }\n\n          $storedMollieId = $this->resolveStoredMollieId($order);\n  \n          // Reject any webhook whose Mollie id does not match the one stored for this order.\n          // 200 is intentional: Mollie retries on any non-2xx response.\n          if (null === $storedMollieId || $storedMollieId !== (string) $molliePaymentId) {\n              return new JsonResponse(null, Response::HTTP_OK);\n          }\n\n          return ($this->inner)($request);\n      }\n\n      private function resolveStoredMollieId(OrderInterface $order): ?string\n      {\n          $payment = $order->getLastPayment();\n          $fromDetails = $payment?->getDetails()['payment_mollie_id'] ?? null;\n          if (null !== $fromDetails && '' !== $fromDetails) {\n              return (string) $fromDetails;\n          }\n  \n          // QR-code flow stores the Mollie id on the order itself.\n          if (method_exists($order, 'getMolliePaymentId')) {\n              $fromOrder = $order->getMolliePaymentId();\n              if (null !== $fromOrder && '' !== $fromOrder) {\n                  return (string) $fromOrder;\n              }\n          }\n  \n          return null;\n      }\n  }\n  ```\n\n  #### Step 2. Register the decorator\n  Append to your project's `config/services.yaml`:\n\n  ```yaml\n  services:\n      App\\Controller\\Mollie\\SecurePaymentWebhookController:\n          decorates: sylius_mollie.controller.shop.payment_webhook\n          public: true\n          arguments:\n              $inner: '@.inner'\n              $orderRepository: '@sylius.repository.order'\n  ```\n\n  > `decorates:` keeps the original service ID, so the route\n  > `_controller: sylius_mollie.controller.shop.payment_webhook` keeps working with no route\n  > changes. `@.inner` is the original plugin controller.\n\n  #### Step 3. Clear the cache\n  ```bash\n  bin/console cache:clear\n  ```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sylius/mollie-plugin"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.2.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sylius/mollie-plugin"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.2.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sylius/mollie-plugin"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.3.0"
      }, {
        "fixed" : "3.3.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/security/advisories/GHSA-rc52-c4hv-w89p"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68500"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/pull/351"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/pull/352"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/pull/354"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/commit/01316b3ad3cf82e3c5ad160115d0a2cf89174e49"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/commit/153c754486b1bc597b67a90ac07ef71cd7958267"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/commit/d1f7753e92106e8bf3bedcfc61b02ea7b8e1c38a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Sylius/MolliePlugin"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/releases/tag/v2.2.8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/releases/tag/v3.2.4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Sylius/MolliePlugin/releases/tag/v3.3.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-31T16:52:39Z",
    "nvd_published_at" : "2026-07-30T21:18:13Z"
  }
}