cveboard RSS feed

CVE-2026-31824

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

Sylius has a Promotion Usage Limit Bypass via Race Condition

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Sylius

Vendor
Sylius
Product
Sylius
Platforms
Unknown
Default status
Unknown
Sylius · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
>= 2.2.0, < 2.2.3affectedUnavailableUnavailableUnavailableNone listed
>= 2.1.0, < 2.1.12affectedUnavailableUnavailableUnavailableNone listed
>= 2.0.0, < 2.0.16affectedUnavailableUnavailableUnavailableNone listed
>= 1.14.0, < 1.14.18affectedUnavailableUnavailableUnavailableNone listed
>= 1.13.0, < 1.13.15affectedUnavailableUnavailableUnavailableNone listed
>= 1.12.0, < 1.12.23affectedUnavailableUnavailableUnavailableNone listed
>= 1.11.0, < 1.11.17affectedUnavailableUnavailableUnavailableNone listed
>= 1.10.0, < 1.10.16affectedUnavailableUnavailableUnavailableNone listed
< 1.9.12affectedUnavailableUnavailableUnavailableNone listed