All vulnerabilities

Servers and applications

CVE-2026-31824

Promotion Usage Limit Bypass via Race Condition

Severity
Medium 5.9
Published
9 Mar 2026
Last changed
17 Jun 2026
Added to UpHeron
1 Nov 2026
Fixed in
1.12.23, 1.13.15, 1.14.18, 2.0.16, 2.1.12, 2.2.3
Exploit chance
0.2% in the next 30 daysHigher than 10% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Race condition (CWE-362)Time-of-check time-of-use race condition (CWE-367)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Change data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Also known as
GHSA-7mp4-25j8-hp5q
Sources
NVD, Project advisories (GitHub)

Description

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 three independent limits:

  • Promotion usage limit - the global used counter on Promotion entities
  • Coupon usage limit - the global used counter on PromotionCoupon entities
  • 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…

From Sylius/Sylius's security advisory. Shortened; the full text is there.

Workarounds

Decoration of the OrderPromotionsUsageModifier service to use atomic operations based on actual database-synchronized values.

The decorated service id in Sylius >=2.0 is sylius.modifier.promotion.order_usage, while <2.0 it's sylius.promotion_usage_modifier; The following instruction uses the latter, but it needs to be changed depending on the Sylius version.

Workarounds as given by Sylius/Sylius's security advisory.

Affected software

SoftwareAffected versions
SyliusServers and applications · cpe:a:sylius:sylius
  • From 2.2.0 before 2.2.3
  • From 2.1.0 before 2.1.12
  • From 2.0.0 before 2.0.16
  • From 1.14.0 before 1.14.18
All 9 release lines
  • Every version before 1.9.12
  • From 1.10.0 before 1.10.16
  • From 1.11.0 before 1.11.17
  • From 1.12.0 before 1.12.23
  • From 1.13.0 before 1.13.15
  • From 1.14.0 before 1.14.18
  • From 2.0.0 before 2.0.16
  • From 2.1.0 before 2.1.12
  • From 2.2.0 before 2.2.3
SyliusServers and applications · github:sylius/sylius
  • Every version before 1.9.12

About Sylius

Headless open-source eCommerce platform on top of PHP/Symfony/API Platform

From its GitHub repository.
Online stores using it
10 000+Sylius
Monthly downloads (Packagist)
173,262Packagist, 15 Nov 2026
Total downloads (Packagist)
6,561,739Packagist, 15 Nov 2026
GitHub stars
8,571GitHub, 15 Nov 2026
Forks
2,167GitHub, 15 Nov 2026
Latest release
v2.3.2GitHub, 15 Nov 2026
Released
22 Oct 2026GitHub
License
MITGitHub
First published on GitHub
5 Nov 2011GitHub

Release lines

ReleaseLatestSecurity fixes
2.32.3.2Until 31 Dec 2027
2.22.2.12Until 31 Mar 2027
2.12.1.17Ended 30 Sept 2026
2.02.0.18Ended 28 Feb 2026
1.14 (LTS)LTS1.14.21Until 31 Dec 2026
1.131.13.17Ended 30 Apr 2025

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-31824
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-31824
  • GitHub Advisory Database https://github.com/advisories/GHSA-7mp4-25j8-hp5q
  • github.com https://github.com/Sylius/Sylius/security/advisories/GHSA-7mp4-25j8-hp5q