Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-53638Published 2026-09-08

CVE-2026-53638 — Sylius

medium

As of 2026-09-08, CVE-2026-53638 is a MEDIUM-severity vulnerability in Sylius, CVSS v3.1 4.3, EPSS 0.1% (7.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-53638 as of 2026-09-08; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
4.3/10Medium
EPSS
0.1%Higher than 7.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.4/10Threadlinqs triage score
Published
CVSS v3.1 4.3 (MEDIUM) · EPSS 0.1% (higher than 7.4% of all scored CVEs) · Priority 2.4/10 · Published 2026-09-08

Last updated:

What is CVE-2026-53638?

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.

The record classifies CVE-2026-53638 under weakness class CWE-863. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 27 days ago.

Severity and exploitation probability

CVSS v3.1 base score
4.3 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 7.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-08

Is CVE-2026-53638 being exploited?

It currently carries a trending score of 32 in the Threadlinqs vulnerability feed.

Affected products and versions

  • Sylius: Sylius

How to fix CVE-2026-53638

No vendor patch reference has been recorded for CVE-2026-53638 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-53638

No threat campaign in the Threadlinqs corpus currently references CVE-2026-53638, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch