vulns.co
/
GKData.io MCP and API Buy me a coffee

Sylius

Sylius: promotion entitlement must be checked and consumed atomically

Sylius could exceed promotion limits because eligibility checks and recorded usage were not kept in sync during overlapping orders. The maintainer describes stale counts and lost concurrent updates affecting promotion-wide, coupon and per-customer limits. A limited promotion or coupon is required, but authentication is not; financial loss is a possible consequence rather than a measured production incident.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Editorial lesson: check the remaining allowance and record its use as one serialized decision, so overlapping orders cannot consume the same allowance. Correct usage counts alone do not prove that an order was eligible when it completed. In owned local models, verify that committed usage stays within the authorized limit and that coupon reuse after cancellation follows the configured policy.

Before reading

  • Basic authorization, application state machines and database transaction concepts

Context and limits

  • The maintainer reports limit overruns without required authentication; a limited promotion or coupon and overlapping order processing are prerequisites. Financial loss is a potential consequence, not a measured production incident.
  • The advisory lists fixes in 1.9.12, 1.10.16, 1.11.17, 1.12.23, 1.13.15, 1.14.18, 2.0.16, 2.1.12 and 2.2.3. Consult its branch-specific affected ranges. Patch dates are not asserted; resource edition remains null.
  • NoResponseMate published the advisory. Reporters are Djibril Mounkoro (whiteov3rflow) and Bartłomiej Nowiński (bnBart); CVE-2026-31824.

Sources

  1. Promotion Usage Limit Bypass via Race ConditionSylius · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software