Sylius: Cart FormComponent allows modification or deletion of an already-completed order

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-53637: 0.36% estimated exploitation activity in the next 30 days; percentile 30.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A user opens the cart page in the browser. In the background, the order gets completed, e.g. an admin changes the status, or the user finalizes payment in another tab. The browser still displays the old cart: the LiveComponent is unaware the underlying order state has changed. If the user then: - clears the cart → clearCart() calls manager-remove() on the completed order: the order is permanently deleted from the database; - removes a product → removeItem() mutates an item on the completed order; - changes quantity → saveCart() overwrites data on the completed order. In all cases, the customer's order data is irreversibly corrupted or lost, even though the order has already been placed and paid for. The same vector can be triggered deliberately by an authenticated customer (keep the cart page open, complete checkout in another tab, then modify the "cart" to add quantity beyond what was paid for). Patches The issue is fixed in versions: 2.0.18, 2.1.15, 2.2.6 and above.…

Published by the source

9 Jul 2026, 21:03 UTC

Last modified by the source

9 Jul 2026, 21:03 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5597-7rmh-97q5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-53637

Advisory: Sylius: Cart FormComponent allows modification or deletion of an already-completed order
IDs: CVE-2026-53637, GHSA-5597-7rmh-97q5
Record: https://patchnext.com/advisories/cve-2026-53637 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sylius/sylius 2.2.6, 2.1.15, 2.0.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sylius/sylius: affected >= 2.0.0, < 2.0.18; >= 2.1.0, < 2.1.15; >= 2.2.0, < 2.2.6; fixed in 2.0.18, 2.2.6, 2.1.15

## Suggested inspection (read-only)
- Packagist sylius/sylius: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sylius/sylius.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5597-7rmh-97q5 (GitHub-reviewed advisory GHSA-5597-7rmh-97q5 lists affected ranges: Packagist sylius/sylius >=2.0.0 =2.1.0 =2.2.0 <2.2.6)

Commands are suggestions: review each one before running it.