CVE-2026-53637Network attack vector

Completed-order corruption via stale cart state

Published Sep 8, 2026 · Updated Sep 9, 2026

Improper workflow enforcement in Sylius allows remote authenticated users to alter or delete already-completed orders. The cart FormComponent retains a stale LiveComponent resource after checkout and lets clearCart(), removeItem(), and saveCart() remove or overwrite the completed order without rechecking its checkout state. Exploitation requires a customer account and a cart page left open while the same order is completed elsewhere; the resulting database changes can corrupt paid-order contents or permanently delete the order.

CVSS severity6.5
Medium
EPSS probability0.29%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper workflow enforcement in Sylius allows remote authenticated users to alter or delete already-completed orders. The cart FormComponent retains a stale LiveComponent resource after checkout and lets clearCart(), removeItem(), and saveCart() remove or overwrite the completed order without rechecking its checkout state. Exploitation requires a customer account and a cart page left open while the same order is completed elsewhere; the resulting database changes can corrupt paid-order contents or permanently delete the order.

The record

CVE
CVE-2026-53637
Published
Sep 8, 2026
Updated
Sep 9, 2026
Vendor
Sylius
Product
Sylius
Classifications
CWE-672, CWE-841, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 9, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 2.0.0, < 2.0.18
  2. Affected versionversion=>= 2.1.0, < 2.1.15
  3. Affected versionversion=>= 2.2.0, < 2.2.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Sylius · Syliusversion=>= 2.0.0, < 2.0.18; version=>= 2.1.0, < 2.1.15; version=>= 2.2.0, < 2.2.6

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-672Operation on a Resource after Expiration or Release
CWE-841Improper Enforcement of Behavioral Workflow
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo