CVE-2026-53638: Sylius authorization bypass in shop account orders API

CVE-2026-53638 · Severity: medium · CVSS 4.3 · Published 2026-09-08

Sylius is an open-source e-commerce platform. A vulnerability in its shop account API allows logged-in customers to bypass payment method restrictions. Specifically, a customer could change their order's payment method to one that the store owner has disabled for that specific sales channel, potentially allowing the use of unauthorized or unintended payment options.

Technologies: sylius/sylius (Packagist), Sylius. Vendors: Packagist, Sylius.

Quick answers

Is CVE-2026-53638 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-53638 being exploited in the wild.
How severe is CVE-2026-53638?
Medium severity, with a CVSS score of 4.3, published 8 September 2026.
Which products and versions are affected?
sylius/sylius (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.18; Sylius >= 2.0.0, < 2.0.18; >= 2.1.0, < 2.1.15; >= 2.2.0, < 2.2.6.
Is there a fix for CVE-2026-53638?
Yes. sylius/sylius (Packagist): upgrade to 2.0.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53638 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-53638?
Check whether you run sylius/sylius (Packagist) or Sylius at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • sylius/sylius (Packagist): upgrade to 2.0.18 or later
    composer require sylius/sylius:^2.0.18

Technical details

An authorization bypass vulnerability exists in the Sylius shop account API due to missing validation in the `PATCH /api/v2/shop/account/orders/{tokenValue}/payments/{paymentId}` endpoint. While the standard checkout endpoint correctly validates payment methods against the order's channel, the account endpoint fails to perform this check for orders in the `STATE_NEW` status. An authenticated attacker can exploit this by sending a PATCH request to assign any globally enabled payment method to their order, even if that method is explicitly restricted from the order's channel. This issue is rooted in the `PaymentMethodChanger` implementation and is fixed in versions 2.0.18, 2.1.15, and 2.2.6.

Affected products

  • Sylius Sylius/Sylius >= 2.0.0, < 2.0.18; >= 2.1.0, < 2.1.15; >= 2.2.0, < 2.2.6

Identifiers

  • CVE-2026-53638
  • GHSA-6955-hrm5-c4qp

Timeline

  • 2026-06-02: disclosed
  • 2026-07-09: advisory
  • 2026-07-09: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.