GHSA-6955-hrm5-c4qp: Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint
An authorization bypass vulnerability exists in the Sylius shop account API endpoint that allows authenticated customers to assign payment methods to their orders that are not enabled for the order's sales channel. This occurs because the PATCH /api/v2/shop/account/orders/{tokenValue}/payments/{paymentId} endpoint does not validate channel restrictions on payment methods, unlike the equivalent checkout endpoint. The issue affects Sylius versions prior to 2.0.18, 2.1.15, and 2.2.6. A fix is available in these versions and above. A workaround involves decorating the PaymentMethodChangerInterface service to enforce channel checks.
AI Analysis
Technical Summary
Sylius contains an authorization bypass vulnerability (CVE-2026-53638) in its shop account API where the PATCH endpoint for modifying payment methods on placed but unpaid orders does not verify that the selected payment method is enabled for the order's channel. This allows authenticated customers to assign any globally enabled payment method to their orders, including those explicitly excluded from the channel. The equivalent checkout endpoint correctly enforces channel restrictions. The vulnerability affects Sylius versions >=2.0.0 <2.0.18, >=2.1.0 <2.1.15, and >=2.2.0 <2.2.6. The issue is fixed in versions 2.0.18, 2.1.15, and 2.2.6 and later. A recommended workaround is to decorate the PaymentMethodChangerInterface service to add channel validation until the patch can be applied.
Potential Impact
An authenticated customer can bypass channel-based payment method restrictions on their own placed orders that are not yet paid, potentially using payment methods the store operator has excluded from the order's channel. This could lead to unintended payment method usage but does not affect confidentiality or availability.
Mitigation Recommendations
A fix is available in Sylius versions 2.0.18, 2.1.15, 2.2.6 and above. Users should upgrade to these versions to remediate the vulnerability. If immediate upgrade is not possible, users can implement the provided workaround by decorating the PaymentMethodChangerInterface service to enforce channel-based payment method validation. This decorator throws a validation exception if the payment method is not supported by the order's channel, effectively mitigating the issue.
GHSA-6955-hrm5-c4qp: Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint
Description
An authorization bypass vulnerability exists in the Sylius shop account API endpoint that allows authenticated customers to assign payment methods to their orders that are not enabled for the order's sales channel. This occurs because the PATCH /api/v2/shop/account/orders/{tokenValue}/payments/{paymentId} endpoint does not validate channel restrictions on payment methods, unlike the equivalent checkout endpoint. The issue affects Sylius versions prior to 2.0.18, 2.1.15, and 2.2.6. A fix is available in these versions and above. A workaround involves decorating the PaymentMethodChangerInterface service to enforce channel checks.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Sylius contains an authorization bypass vulnerability (CVE-2026-53638) in its shop account API where the PATCH endpoint for modifying payment methods on placed but unpaid orders does not verify that the selected payment method is enabled for the order's channel. This allows authenticated customers to assign any globally enabled payment method to their orders, including those explicitly excluded from the channel. The equivalent checkout endpoint correctly enforces channel restrictions. The vulnerability affects Sylius versions >=2.0.0 <2.0.18, >=2.1.0 <2.1.15, and >=2.2.0 <2.2.6. The issue is fixed in versions 2.0.18, 2.1.15, and 2.2.6 and later. A recommended workaround is to decorate the PaymentMethodChangerInterface service to add channel validation until the patch can be applied.
Potential Impact
An authenticated customer can bypass channel-based payment method restrictions on their own placed orders that are not yet paid, potentially using payment methods the store operator has excluded from the order's channel. This could lead to unintended payment method usage but does not affect confidentiality or availability.
Mitigation Recommendations
A fix is available in Sylius versions 2.0.18, 2.1.15, 2.2.6 and above. Users should upgrade to these versions to remediate the vulnerability. If immediate upgrade is not possible, users can implement the provided workaround by decorating the PaymentMethodChangerInterface service to enforce channel-based payment method validation. This decorator throws a validation exception if the payment method is not supported by the order's channel, effectively mitigating the issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6955-hrm5-c4qp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53638"]
- Ecosystems
- ["Packagist"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a50ba7168715ace43580102
Added to database: 07/10/2026, 09:25:05 UTC
Last enriched: 07/10/2026, 09:53:36 UTC
Last updated: 07/10/2026, 18:40:12 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.