Answer in brief
CVE-2026-53638 records a Medium severity (CVSS 4.3) vulnerability in Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint. The current sources do not mark it as known exploited. The current feed maps sylius/sylius (composer), sylius/sylius (composer), sylius/sylius (composer), Sylius/Sylius (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps sylius/sylius (composer), sylius/sylius (composer), sylius/sylius (composer), Sylius/Sylius (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| sylius/syliuscomposer | >=2.2.0,<2.2.6 | 2.2.6 |
| sylius/syliuscomposer | >=2.0.0,<2.0.18 | 2.0.18 |
| sylius/syliuscomposer | >=2.1.0,<2.1.15 | 2.1.15 |
| Sylius/Syliusgeneric | >= 2.0.0, < 2.0.18 || >= 2.1.0, < 2.1.15 || >= 2.2.0, < 2.2.6 | Not reported |
Published upstream
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.