CVE-2026-31820
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSylius is an Open Source eCommerce Framework on Symfony. An authenticated Insecure Direct Object Reference (IDOR) vulnerability exists in multiple shop LiveComponents due to unvalidated resource IDs accepted via #[LiveArg] parameters. Unlike props, which are protected by LiveComponent's @checksum, args are fully user-controlled - any action that accepts a resource ID via #[LiveArg] and loads it with ->find() without ownership validation is vulnerable. Checkout address FormComponent (addressFieldUpdated action): Accepts an addressId via #[LiveArg] and loads it without verifying ownership, exposing another user's first name, last name, company, phone number, street, city, postcode, and country. Cart WidgetComponent (refreshCart action): Accepts a cartId via #[LiveArg] and loads any order directly from the repository, exposing order total and item count. Cart SummaryComponent (refreshCart action): Accepts a cartId via #[LiveArg] and loads any order directly from the repository, exposing subtotal, discount, shipping cost, taxes (excluded and included), and order total. Since sylius_order contains both active carts (state=cart) and completed orders (state=new/fulfilled) in the same ID space, the cart IDOR exposes data from all orders, not just active carts. The issue is fixed in versions: 2.0.16, 2.1.12, 2.2.3 and above.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIDOR vulnerability in Sylius LiveComponents where authenticated users can access other users' address and cart data by manipulating resource IDs passed via #[LiveArg] parameters. The checkout address FormComponent, Cart WidgetComponent, and Cart SummaryComponent all load resources via ->find() without ownership validation, exposing sensitive personal and order information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0.0, < 2.0.16>= 2.1.0, < 2.1.12>= 2.2.0, < 2.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Sylius versionRun 'composer show sylius/sylius-core' or inspect your composer.lock file to find the installed version of sylius/sylius-coreAffected if The version is >= 2.0.0 and < 2.0.16, OR >= 2.1.0 and < 2.1.12, OR >= 2.2.0 and < 2.2.3
-
Identify LiveComponent usage in checkout addressSearch your codebase for files named 'CheckoutAddressFormComponent.php' or similar patterns in src/ and vendor/ directories that contain #[LiveArg] and ->find() calls without ownership checksAffected if The checkout address component uses #[LiveArg] to accept resource IDs and loads resources via ->find() without validating ownership
-
Identify LiveComponent usage in cart componentsSearch for WidgetComponent and CartSummaryComponent classes that use LiveComponents with #[LiveArg] parameters, looking for ->find() calls on cart or address resourcesAffected if Cart-related LiveComponents accept resource IDs via #[LiveArg] and load data without ownership validation
-
Verify ownership validation existsReview the vulnerable component methods: grep for 'find(' within LiveComponent classes and verify there is a check like '->getCustomer() === $this->getUser()' or similar ownership validation before returning dataAffected if No ownership validation exists before returning cart or address data via LiveComponent methods that accept resource IDs as parameters
You are affected if your Sylius version is in the vulnerable range AND your codebase contains the LiveComponent classes (checkout address, cart widget, or cart summary) that accept resource IDs via #[LiveArg] without ownership validation checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.162.1.122.2.3
Upgrade to Sylius versions 2.0.16, 2.1.12, 2.2.3 or above. Alternatively, implement ownership validation checks in all LiveComponent methods that accept resource IDs via #[LiveArg] before loading from the repository.
2.0.16, 2.1.12, or 2.2.3 depending on your current branch
- Identify your current Sylius version by checking your composer.json or installed version
- If using Sylius 2.0.x: Run `composer require sylius/sylius:2.0.16 --no-interaction --no-update` then `composer update sylius/sylius`
- If using Sylius 2.1.x: Run `composer require sylius/sylius:2.1.12 --no-interaction --no-update` then `composer update sylius/sylius`
- If using Sylius 2.2.x: Run `composer require sylius/sylius:2.2.3 --no-interaction --no-update` then `composer update sylius/sylius`
- Clear Symfony cache after upgrade: `php bin/console cache:clear`
- Verify the upgrade by running your test suite and checking that LiveComponent #[LiveArg] parameters now validate ownership before loading resources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31820 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31820 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data