CVE-2026-31824: Sylius has a Promotion Usage Limit Bypass via Race Condition
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: sylius/sylius (Packagist) 1.10.16, 1.11.17, 1.12.23.
- Severity is disputed: the assigning authority (CNA) scores it 8.2, NVD 5.9.
Low priority for now. Upgrade to sylius/sylius (Packagist) 1.10.16, 1.11.17, 1.12.23 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 10, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-362
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.9
- CNA · GitHub_M
- 8.2
- 2.3 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sylius | sylius | cpe:2.3:a:sylius:sylius |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
Sylius Sylius
- >= 2.2.0, < 2.2.3, >= 2.1.0, < 2.1.12, >= 2.0.0, < 2.0.16, >= 1.14.0, < 1.14.18, >= 1.13.0, < 1.13.15, >= 1.12.0, < 1.12.23, >= 1.11.0, < 1.11.17, >= 1.10.0, < 1.10.16, < 1.9.12affected
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sylius syliusbefore 1.9.12
- sylius sylius1.10.0 and later · before 1.10.16
- sylius sylius1.11.0 and later · before 1.11.17
- sylius sylius1.12.0 and later · before 1.12.23
- sylius sylius1.13.0 and later · before 1.13.15
- sylius sylius1.14.0 and later · before 1.14.18
- sylius sylius2.0.0 and later · before 2.0.16
- sylius sylius2.1.0 and later · before 2.1.12
- sylius sylius2.2.0 and later · before 2.2.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | sylius/sylius | from 1.10.0 · before 1.10.16 | 1.10.16 |
| Packagist | sylius/sylius | from 1.11.0 · before 1.11.17 | 1.11.17 |
| Packagist | sylius/sylius | from 1.12.0 · before 1.12.23 | 1.12.23 |
| Packagist | sylius/sylius | from 1.13.0 · before 1.13.15 | 1.13.15 |
| Packagist | sylius/sylius | from 1.14.0 · before 1.14.18 | 1.14.18 |
| Packagist | sylius/sylius | from 2.0.0 · before 2.0.16 | 2.0.16 |
| Packagist | sylius/sylius | from 2.1.0 · before 2.1.12 | 2.1.12 |
| Packagist | sylius/sylius | from 2.2.0 · before 2.2.3 | 2.2.3 |
| Packagist | sylius/sylius | before 1.9.12 | 1.9.12 |
Same product
sylius: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-100872Sylius 2.x before 2.1.16 and 2.2.9 Payment Amount Overwrite34Monitor
- CVE-2026-100871Sylius before 1.12.25, 1.13.17, 1.14.20, 2.1.16, and 2.2.9 JWT Audience Confusion Allows Admin API Authentication34Monitor
- CVE-2026-100870Sylius before 1.12.25, 1.13.17, 1.14.20, 2.1.16, and 2.2.9 Admin Password Reset Poisoning via Host Header34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-31822Mar 10, 2026 · Sylius has a XSS vulnerability in checkout login form21Monitor
- ← EarlierCVE-2026-31823Mar 10, 2026 · Sylius has Authenticated Stored XSS19Monitor
- Later →CVE-2026-31825Mar 10, 2026 · Sylius has a DQL Injection via API Order Filters21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:sylius/sylius | 1.10.16 | Package registry (OSV) |
| Packagist:sylius/sylius | 1.11.17 | Package registry (OSV) |
| Packagist:sylius/sylius | 1.12.23 | Package registry (OSV) |
| Packagist:sylius/sylius | 1.13.15 | Package registry (OSV) |
| Packagist:sylius/sylius | 1.14.18 | Package registry (OSV) |
| Packagist:sylius/sylius | 1.9.12 | Package registry (OSV) |
| Packagist:sylius/sylius | 2.0.16 | Package registry (OSV) |
| Packagist:sylius/sylius | 2.1.12 | Package registry (OSV) |
| Packagist:sylius/sylius | 2.2.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.