dbcve.org
SyliusApplication

CVE-2026-31824

MEDIUM · 5.9 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.9.12 / 1.10.16 or later.
See remediation →
68/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. A Time-of-Check To Time-of-Use (TOCTOU) race condition was discovered in the promotion usage limit enforcement. The same class of vulnerability affects the promotion usage limit (the global used counter on Promotion entities), coupon usage limit (the global used counter on PromotionCoupon entities), and coupon per-customer usage limit (the per-customer redemption count on PromotionCoupon entities). In all three cases, the eligibility check reads the used counter (or order count) from an in-memory Doctrine entity during validation, while the actual usage increment in OrderPromotionsUsageModifier happens later during order completion — with no database-level locking or atomic operations between the two phases. Because Doctrine flushes an absolute value (SET used = 1) rather than an atomic increment (SET used = used + 1), and because the affected entities lack optimistic locking, concurrent requests all read the same stale usage counts and pass the eligibility checks simultaneously. An attacker can exploit this by preparing multiple carts with the same limited-use promotion or coupon and firing simultaneous PATCH /api/v2/shop/orders/{token}/complete requests. All requests pass the usage limit checks and complete successfully, allowing a single-use promotion or coupon to be redeemed an arbitrary number of times. The per-customer limit can be bypassed in the same way by a single customer completing multiple orders concurrently. No authentication is required to exploit this vulnerability. This may lead to direct financial loss through unlimited redemption of limited-use promotions and discount coupons. The issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.23, 1.13.15, 1.14.18, 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

A TOCTOU race condition in Sylius allows bypassing promotion and coupon usage limits. The usage check reads from in-memory Doctrine entities during validation, while the actual increment happens later during order completion. Since Doctrine uses absolute value assignments rather than atomic increments and lacks optimistic locking, concurrent requests read stale usage counts and pass eligibility checks simultaneously.

MitigationApply the appropriate patched version (1.9.12+, 1.10.16+, 1.11.17+, 1.12.23+, 1.13.15+, 1.14.18+, 2.0.16+, 2.1.12+, or 2.2.3+) for the installed release line to receive the vendor fix.

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:< 1.9.12>= 1.10.0, < 1.10.16>= 1.11.0, < 1.11.17>= 1.12.0, < 1.12.23>= 1.13.0, < 1.13.15>= 1.14.0, < 1.14.18>= 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 composer.json file in the project root and check the 'sylius/sylius' package version, or run 'composer show sylius/sylius | grep version' in the project directory
    Affected if The version falls within any of these ranges: < 1.9.12, >= 1.10.0 < 1.10.16, >= 1.11.0 < 1.11.17, >= 1.12.0 < 1.12.23, >= 1.13.0 < 1.13.15, >= 1.14.0 < 1.14.18, >= 2.0.0 < 2.0.16, >= 2.1.0 < 2.1.12, or >= 2.2.0 < 2.2.3
  2. Check if promotions are used
    Query the database for active promotions: look in the 'sylius_promotion' table for records with 'enabled' set to true, or inspect the application's promotion configuration files
    Affected if Promotions are enabled and in use on the storefront
  3. Check if coupons are in use
    Query the 'sylius_promotion_coupon' table to see if any coupons exist, or review order history for coupon usage in 'sylius_order' table
    Affected if Promotion coupons are configured and being applied to orders
  4. Verify database locking configuration
    Check the Doctrine entity configuration for PromotionCoupon or PromotionSubject entities for 'version' or 'locking' attributes. Inspect config/packages/doctrine.yaml for optimistic locking settings
    Affected if No optimistic locking (version field) is configured on promotion-related entities, AND the Sylius version is in the affected range

The environment is affected if Sylius version is within the vulnerable ranges AND promotions with usage limits or coupons are actively used on the storefront, since the race condition allows bypassing those limits under concurrent requests.

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 1.9.12 / 1.10.16 / 1.11.17 or later
Fixed in 1.9.121.10.161.11.17
Interim mitigation

Apply the appropriate patched version (1.9.12+, 1.10.16+, 1.11.17+, 1.12.23+, 1.13.15+, 1.14.18+, 2.0.16+, 2.1.12+, or 2.2.3+) for the installed release line to receive the vendor fix.

Recommended fix High confidence

Upgrade to the latest version in your current major branch: 1.9.12 (if on 1.9.x), 1.10.16 (if on 1.10.x), 1.11.17 (if on 1.11.x), 1.12.23 (if on 1.12.x), 1.13.15 (if on 1.13.x), 1.14.18 (if on 1.14.x), 2.0.16 (if on 2.0.x), 2.1.12 (if on 2.1.x), or 2.2.3+ (if on 2.2.x)

  1. Identify the currently installed Sylius version by checking your composer.json or composer.lock file
  2. Run 'composer show sylius/sylius | grep version' to confirm the exact version
  3. Determine the appropriate upgrade path based on your current major version (1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x, 1.14.x, 2.0.x, 2.1.x, or 2.2.x)
  4. Run 'composer require sylius/sylius:^<target_version> --no-interaction' replacing <target_version> with the minimum fixed version for your branch (e.g., 1.12.23 for 1.12.x)
  5. Allow Composer to resolve dependencies and update the sylius/sylius package
  6. Run 'composer update --no-interaction' to apply all changes
  7. Clear the application cache with 'php bin/console cache:clear' or 'php bin/console cache:clear --env=prod'
  8. Run database migrations if any are required: 'php bin/console doctrine:migrations:migrate --no-interaction'
Caveat Minor version upgrades within the same major version should have minimal breaking changes; however, review the Sylius changelog for your version branch to check for any deprecated features or configuration changes before upgrading

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

Fix this in Sylius Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31824 — 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-31824 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