FKIE_CVE-2026-31824
Vulnerability from fkie_nvd - Published: 2026-03-10 22:16 - Updated: 2026-03-11 19:30
Severity ?
8.2 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
5.9 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
5.9 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Summary
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.
References
| URL | Tags | ||
|---|---|---|---|
| security-advisories@github.com | https://github.com/Sylius/Sylius/security/advisories/GHSA-7mp4-25j8-hp5q | Mitigation, Vendor Advisory |
{
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "51770D35-6AE8-496E-96BC-66EB6BCE7B40",
"versionEndExcluding": "1.9.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "2A470C5F-0EA5-44E7-8972-DBD12E239521",
"versionEndExcluding": "1.10.16",
"versionStartIncluding": "1.10.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "7BA83BA2-99AF-472A-A1A0-C3E816124261",
"versionEndExcluding": "1.11.17",
"versionStartIncluding": "1.11.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "429D1774-7663-41CF-97B5-864341D416B6",
"versionEndExcluding": "1.12.23",
"versionStartIncluding": "1.12.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "90B50358-6686-4FCC-AFC3-581927B851A3",
"versionEndExcluding": "1.13.15",
"versionStartIncluding": "1.13.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "8FC1AC20-9138-4CF3-81F5-A0CA777A693E",
"versionEndExcluding": "1.14.18",
"versionStartIncluding": "1.14.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "DA9449ED-A73A-4D16-A464-DBCBE24CA6A6",
"versionEndExcluding": "2.0.16",
"versionStartIncluding": "2.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "F45888BF-720D-4B78-BA7D-ED7E5E091A8C",
"versionEndExcluding": "2.1.12",
"versionStartIncluding": "2.1.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sylius:sylius:*:*:*:*:*:*:*:*",
"matchCriteriaId": "9A2540B0-56B9-4B15-9876-BE908A80BB0A",
"versionEndExcluding": "2.2.3",
"versionStartIncluding": "2.2.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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 \u2014 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."
},
{
"lang": "es",
"value": "Sylius es un framework de comercio electr\u00f3nico de C\u00f3digo Abierto sobre Symfony. Se descubri\u00f3 una condici\u00f3n de carrera Time-of-Check To Time-of-Use (TOCTOU) en la aplicaci\u00f3n del l\u00edmite de uso de promociones. La misma clase de vulnerabilidad afecta el l\u00edmite de uso de promociones (el contador global de uso en las entidades de Promoci\u00f3n), el l\u00edmite de uso de cupones (el contador global de uso en las entidades de PromotionCoupon) y el l\u00edmite de uso de cupones por cliente (el recuento de canjes por cliente en las entidades de PromotionCoupon). En los tres casos, la verificaci\u00f3n de elegibilidad lee el contador de uso (o el recuento de pedidos) de una entidad Doctrine en memoria durante la validaci\u00f3n, mientras que el incremento de uso real en OrderPromotionsUsageModifier ocurre m\u00e1s tarde durante la finalizaci\u00f3n del pedido, sin bloqueo a nivel de base de datos ni operaciones at\u00f3micas entre las dos fases. Debido a que Doctrine vac\u00eda un valor absoluto (SET used = 1) en lugar de un incremento at\u00f3mico (SET used = used + 1), y debido a que las entidades afectadas carecen de bloqueo optimista, todas las solicitudes concurrentes leen los mismos recuentos de uso obsoletos y pasan las verificaciones de elegibilidad simult\u00e1neamente. Un atacante puede explotar esto preparando m\u00faltiples carritos con la misma promoci\u00f3n o cup\u00f3n de uso limitado y enviando solicitudes PATCH /api/v2/shop/orders/{token}/complete simult\u00e1neas. Todas las solicitudes pasan las verificaciones del l\u00edmite de uso y se completan con \u00e9xito, permitiendo que una promoci\u00f3n o cup\u00f3n de un solo uso sea canjeado un n\u00famero arbitrario de veces. El l\u00edmite por cliente puede ser eludido de la misma manera por un solo cliente que complete m\u00faltiples pedidos concurrentemente. No se requiere autenticaci\u00f3n para explotar esta vulnerabilidad. Esto puede llevar a una p\u00e9rdida financiera directa a trav\u00e9s del canje ilimitado de promociones de uso limitado y cupones de descuento. El problema est\u00e1 solucionado en las versiones: 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 y superiores."
}
],
"id": "CVE-2026-31824",
"lastModified": "2026-03-11T19:30:24.990",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 8.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 4.2,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2026-03-10T22:16:20.137",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/Sylius/Sylius/security/advisories/GHSA-7mp4-25j8-hp5q"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-362"
},
{
"lang": "en",
"value": "CWE-367"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-367"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…