VulnerabilityPublished 9 Jul 2026

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

Affects sylius/syliusSource GCVE Database

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.0.18 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.0.18, 2.1.15, 2.2.6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade sylius/sylius to 2.0.18; sylius/sylius to 2.1.15; sylius/sylius to 2.2.6.

Affected software

Product	Affected	Fixed in
Packagistsylius/sylius	Affected >=2.0.0 <2.0.18	Fixed in 2.0.18
Packagistsylius/sylius	Affected >=2.1.0 <2.1.15	Fixed in 2.1.15
Packagistsylius/sylius	Affected >=2.2.0 <2.2.6	Fixed in 2.2.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Sylius versions 2.0.18, 2.1.15, and 2.2.6 and above. Users should upgrade to these versions or later to resolve the issue. If immediate upgrade is not possible, a workaround involves creating a patched copy of the affected Cart FormComponent class in the application source directory and overriding the Sylius service definition to use the patched class, as detailed in the vendor advisory.

Description

Sylius versions prior to 2.0.18, 2.1.15, and 2.2.6 contain a vulnerability in the Cart FormComponent that allows modification or deletion of an already-completed order. This occurs because the cart page in the browser does not reflect changes made to the order status in the background, allowing actions such as clearing the cart, removing products, or changing quantities to corrupt or delete completed order data irreversibly.

Impact

An attacker or legitimate user can cause irreversible loss or corruption of completed order data by manipulating the cart page after the order has been finalized. This can lead to deletion of completed orders or unauthorized modification of order contents, potentially impacting order integrity and customer trust. There is no direct confidentiality or availability impact reported, but integrity is severely affected.

Summary

The Sylius Cart FormComponent does not properly handle state changes when an order is completed in the background (e.g., by an admin or payment finalization in another tab). The LiveComponent displaying the cart remains unaware of the order's completed state, allowing users to perform actions like clearing the cart, removing items, or changing quantities on an order that is already completed. These actions result in permanent deletion or corruption of the order data in the database. The vulnerability affects Sylius versions >=2.0.0 <2.0.18, >=2.1.0 <2.1.15, and >=2.2.0 <2.2.6. The issue is fixed in versions 2.0.18, 2.1.15, and 2.2.6 and later.

CWE-672Operation on a Resource after Expiration or Release (opens in a new tab)
Class weakness
The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.
CWE-841Improper Enforcement of Behavioral Workflow (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence or timeframe.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.1 (opens in a new tab)
V11.1.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2026, 09:53 UTC

WeaknessesCWE-672, CWE-841

Technical details

References

Community reviews

Related threats