Servers and applications
CVE-2026-100872
Order total can be inflated after a Payment Request has started a gateway transaction, marking the order fully paid
- Severity
- High 7.5
- Published
- 2 Sept 2026
- Last changed
- 26 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 2.1.16, 2.2.9
- Exploit chance
- 0.2% in the next 30 daysHigher than 12% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N- Also known as
- GHSA-vv4h-q2x8-74g4
- Sources
- Project advisories (GitHub)
Description
A guest, with no authentication and no administrator involvement, could pay a small, legitimate amount for an order, enlarge that same order after the payment gateway had already captured the funds, and have Sylius mark the enlarged order as fully paid, while the gateway's ledger showed only the original, much smaller capture.
The root cause is in OrderPaymentProcessor. On every cart recalculation it took the last payment in the target state and rewrote its amount and currencyCode to the order's current total, with no check for whether that payment had already been handed to a gateway. OrderPaymentsRemover had the mirror problem: it deleted any cart-state payment once the total reached zero, again without checking whether a gateway transaction was already in flight against it.
Workarounds
If you cannot update Sylius immediately, decorate the affected services.
Affected software
| Software | Affected versions |
|---|---|
SyliusServers and applications · github:sylius/sylius |
|
About Sylius
Headless open-source eCommerce platform on top of PHP/Symfony/API Platform
- 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
| Release | Latest | Security fixes |
|---|---|---|
| 2.3 | 2.3.2 | Until 31 Dec 2027 |
| 2.2 | 2.2.12 | Until 31 Mar 2027 |
| 2.1 | 2.1.17 | Ended 30 Sept 2026 |
| 2.0 | 2.0.18 | Ended 28 Feb 2026 |
| 1.14 (LTS)LTS | 1.14.21 | Until 31 Dec 2026 |
| 1.13 | 1.13.17 | Ended 30 Apr 2025 |
From endoflife.date.
Vulnerabilities in Sylius
- In our list
- 35
- Published in the last 12 months
- 21
- Critical, last 12 months
- 0
- High, last 12 months
- 7
- Known exploited
- 0
- GHSA-ccgh-6w73-crf8Channel-based payment method restriction bypass on shop payment request API endpointMedium 4.3 22 Oct 2026
- GHSA-h76r-rr27-3gm4Promotion and coupon Usage Limit Bypass via Race ConditionHigh 8.2 22 Oct 2026
- GHSA-5mpg-w6q2-2vrwUnpublished product reviews disclosed through the Shop API item endpointMedium 5.3 22 Oct 2026
- GHSA-v78h-66q4-h9pxHost header injection in the shop password reset e-mail link when the channel has no hostnameHigh 8.1 22 Oct 2026
- GHSA-cqw6-3fwg-cfv4Percent-encoded API path bypasses shop API ownership filters, exposing and modifying other customers' dataHigh 8.1 22 Oct 2026
- GHSA-mw28-p745-4jrvA disabled API stays reachable through a percent-encoded pathMedium 6.5 22 Oct 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-100872
- GitHub Advisory Database https://github.com/advisories/GHSA-vv4h-q2x8-74g4
- github.com https://github.com/Sylius/Sylius/security/advisories/GHSA-vv4h-q2x8-74g4