dbcve.org
SyliusApplication

CVE-2026-31821

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 2.0.16 / 2.1.12 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Sylius is an Open Source eCommerce Framework on Symfony. The POST /api/v2/shop/orders/{tokenValue}/items endpoint does not verify cart ownership. An unauthenticated attacker can add items to other registered customers' carts by knowing the cart tokenValue. An attacker who obtains a cart tokenValue can add arbitrary items to another customer's cart. The endpoint returns the full cart representation in the response (HTTP 201). 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 confidence

The POST /api/v2/shop/orders/{tokenValue}/items endpoint in Sylius eCommerce framework lacks proper authorization validation, allowing unauthenticated attackers to add items to any customer's cart by knowing the cart's tokenValue. This enables cart poisoning and potential financial impact through unauthorized order manipulation.

MitigationUpgrade Sylius to version 2.0.16, 2.1.12, 2.2.3 or higher to receive the patch that implements proper cart ownership verification on the order items endpoint.

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
SyliusApplication
Affected:>= 2.0.0, < 2.0.16>= 2.1.0, < 2.1.12>= 2.2.0, < 2.2.3

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Sylius version
    Locate the Sylius version in your project's composer.json file under the 'sylius/sylius' package entry, or check the version file if your deployment method stores it separately
    Affected if The installed version falls within >= 2.0.0, < 2.0.16 OR >= 2.1.0, < 2.1.12 OR >= 2.2.0, < 2.2.3
  2. Confirm API shop endpoints are enabled
    Check your Sylius configuration files (typically config/packages/sylius_shop.yaml or similar) for the enabled API routes under sylius_shop: routing: or verify that api/v2/shop routes are loaded
    Affected if The shop API routes including /api/v2/shop/orders are actively loaded in your application routing
  3. Verify the vulnerable endpoint is accessible
    Test accessing the POST /api/v2/shop/orders/{tokenValue}/items endpoint in your environment (use a test cart token or documentation to understand the route structure)
    Affected if The endpoint responds and accepts POST requests without returning a 401/403 authentication error
  4. Check for missing authorization on cart operations
    Inspect the controller or security configuration handling the /api/v2/shop/orders/{tokenValue}/items route to see if there is an is_granted or similar ownership check validating that the requester owns the cart token provided
    Affected if The endpoint accepts any valid tokenValue without verifying the requester has ownership of that specific cart

You are affected if your Sylius installation version is within the affected ranges AND the shop API is enabled, allowing the /api/v2/shop/orders/{tokenValue}/items endpoint to accept requests without proper cart ownership validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.0.16 / 2.1.12 / 2.2.3 or later
Fixed in 2.0.162.1.122.2.3
Interim mitigation

Upgrade Sylius to version 2.0.16, 2.1.12, 2.2.3 or higher to receive the patch that implements proper cart ownership verification on the order items endpoint.

Recommended fix High confidence

Upgrade to the latest patch version within your current major branch (2.0.16+, 2.1.12+, or 2.2.3+)

  1. 1. Back up your current project database and codebase before making any changes
  2. 2. Identify your current Sylius version by checking composer.json
  3. 3. If using Sylius 2.0.x, update the version constraint in composer.json to ^2.0.16
  4. 4. If using Sylius 2.1.x, update the version constraint in composer.json to ^2.1.12
  5. 5. If using Sylius 2.2.x, update the version constraint in composer.json to ^2.2.3
  6. 6. Run 'composer update sylius/sylius --with-all-dependencies' to install the fixed version
  7. 7. Clear the application cache after updating
  8. 8. Run your test suite to verify the fix works and no regressions were introduced
Caveat Patch releases typically contain only bug and security fixes with minimal breaking changes; review the Sylius changelog for your version to confirm

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sylius Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31821 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31821 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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