Quick answers
- Is CVE-2026-53637 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53637 being exploited in the wild.
- How severe is CVE-2026-53637?
- Medium severity, with a CVSS score of 6.5, 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-53637?
- 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-53637 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53637?
- 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
A vulnerability exists in the Sylius Cart FormComponent where the LiveComponent fails to verify the current state of an order before performing mutations. If a user has a cart page open while the order is completed in another session (e.g., by an admin or a separate payment tab), subsequent actions like clearing the cart, removing items, or changing quantities are executed against the finalized order. This occurs because the `hydrateResource` and action methods do not sufficiently validate that the order is still in a 'cart' state. An attacker can deliberately exploit this to corrupt order data or delete completed records from the database. Patches are available 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-53637
- GHSA-5597-7rmh-97q5
Timeline
- 2026-06-02: disclosed: Initial publication date
- 2026-07-09: advisory: Advisory updated