# CVE-2026-53637: Sylius: Cart FormComponent allows modification or deletion of an already-completed order

> Authenticated users can modify or delete completed orders due to improper workflow enforcement in the cart component.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-5597-7rmh-97q5

## What is CVE-2026-53637?

CVE-2026-53637 is a medium-severity vulnerability in Sylius, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sylius is an Open Source eCommerce Framework on Symfony. Versions 2.0.0 through 2.0.17, 2.1.0 through 2.1.14, and 2.2.0 through 2.2.5 contain an improper workflow enforcement vulnerability in the cart `FormComponent`. When an order is completed while its cart page remains open, the stale LiveComponent does not detect the order’s changed state and continues to permit cart actions, allowing an authenticated customer to modify or permanently delete an already completed order. Versions 2.0.18, 2.1.15, and 2.2.6 contain a patch. As a workaround, deployments can copy the patched `FormComponent` into the application's `src/` directory and override the `sylius_shop.twig.component.cart.form` service definition to use that class.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow), CWE-672 (Operation on a Resource after Expiration or Release)

## Which versions are affected by CVE-2026-53637?

6 open source packages ship an affected version, including sylius/sylius.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sylius/sylius` | Packagist | From 2.0.0 | 2.0.18 |
| `sylius/sylius` | Packagist | From 2.0.0 | 2.0.18 |
| `sylius/sylius` | Packagist | From 2.1.0 | 2.1.15 |
| `sylius/sylius` | Packagist | From 2.1.0 | 2.1.15 |
| `sylius/sylius` | Packagist | From 2.2.0 | 2.2.6 |
| `sylius/sylius` | Packagist | From 2.2.0 | 2.2.6 |

## How do I fix CVE-2026-53637?

Upgrade sylius/sylius to a fixed version for your release line: 2.0.18, 2.1.15 or 2.2.6.

## Is CVE-2026-53637 being exploited?

There is no known exploitation of CVE-2026-53637 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53637 and fix it if it is affected.

What it is: CVE-2026-53637 is a medium-severity vulnerability in Sylius, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53637 in the wild and no public exploit code.

Affected packages and fixed versions:
- sylius/sylius (Packagist): affected from 2.0.0; fixed in 2.0.18
- sylius/sylius (Packagist): affected from 2.0.0; fixed in 2.0.18
- sylius/sylius (Packagist): affected from 2.1.0; fixed in 2.1.15
- sylius/sylius (Packagist): affected from 2.1.0; fixed in 2.1.15
- sylius/sylius (Packagist): affected from 2.2.0; fixed in 2.2.6
- sylius/sylius (Packagist): affected from 2.2.0; fixed in 2.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53637/ (Markdown: https://insights.sbomify.com/CVE-2026-53637/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53637
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53637
- OSV: https://osv.dev/vulnerability/CVE-2026-53637

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53637/
Summaries are generated and may contain mistakes; the official description above is the record.