Sylius versions before 2.1.16 and 2.2.9 fail to validate payment amounts during cart recalculation, allowing unauthenticated attackers to modify order totals after gateway transaction initiation. Attackers can pay a small amount, enlarge the order after gateway capture, and have the system mark the inflated order as fully paid while the gateway captured only the original amount.
CVE-2026-100872
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-27. A secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 65EG Risk 65/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 6th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 27, 2026
Last Modified
September 28, 2026
Advisory Details (6)
Auto-updated Sep 27, 2026Sylius 2.x before 2.1.16 and 2.2.9 Payment Amount Overwrite | Advisories | VulnCheck
https://www.vulncheck.com/advisories/sylius-2-x-before-2.1.16-and-2.2.9-payment-amount-overwriteOrder total can be inflated after a Payment Request has started a gateway transaction, marking the order fully paid · Advisory · Sylius/Sylius · GitHub
Affected: versions: 2.1.16, 2.2.9 and above.
https://github.com/Sylius/Sylius/security/advisories/GHSA-vv4h-q2x8-74g4v2.2.9
Patch available: Sylius/Sylius v2.2.9
https://github.com/Sylius/Sylius/releases/tag/v2.2.9[2.2] Prevent payment amount tampering after a gateway transaction has started
Patch available: Sylius/Sylius v2.2.9 (PR #19216 merged 2026-09-02)
https://github.com/Sylius/Sylius/pull/19216commit 9e9aeaacbc97 (Sylius/Sylius)
Patch available: Sylius/Sylius v2.2.9 (contains commit 9e9aeaacbc97)
https://github.com/Sylius/Sylius/commit/9e9aeaacbc97b1fc01d573e44d6679194527905dGitHub - Sylius/Sylius: Headless open-source eCommerce platform on top of PHP/Symfony/API Platform · GitHub
https://github.com/Sylius/SyliusVendor Advisories for CVE-2026-100872(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 32× in last 7d / 35× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 09:55 UTCGHSA enrichment
- 2026-10-03 22:08 UTCEG score recompute
- 2026-10-03 22:08 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 10:21 UTCGHSA enrichment
- 2026-10-02 22:34 UTCEG score recompute
- 2026-10-02 22:34 UTCGHSA enrichment
- 2026-10-02 10:47 UTCGHSA enrichment
- 2026-10-01 22:57 UTCEG score recompute
- 2026-10-01 22:57 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 11:10 UTCGHSA enrichment
- 2026-09-30 23:24 UTCEG score recompute
- 2026-09-30 23:23 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-30 11:34 UTCGHSA enrichment
- 2026-09-29 23:47 UTCEG score recompute
- 2026-09-29 23:47 UTCGHSA enrichment
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-29 09:04 UTCEG score recompute
- 2026-09-29 09:04 UTCGHSA enrichment
- 2026-09-28 21:13 UTCGHSA enrichment
- 2026-09-28 16:32 UTCEG score recompute
- 2026-09-28 16:32 UTCGHSA enrichment
- 2026-09-28 15:23 UTCEG score recompute
Show 10 moreShow fewer
- 2026-09-28 15:22 UTCGHSA enrichment
- 2026-09-28 14:09 UTCEG score recompute
- 2026-09-28 14:09 UTCGHSA enrichment
- 2026-09-28 13:50 UTCEPSS rescore
- 2026-09-28 02:22 UTCEG score recompute
- 2026-09-28 02:22 UTCGHSA enrichment
- 2026-09-27 14:35 UTCEG score recompute
- 2026-09-27 13:18 UTCEG score recompute
- 2026-09-27 13:16 UTCEG score recompute
- 2026-09-27 13:15 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-100872?
When was CVE-2026-100872 disclosed?
Is CVE-2026-100872 actively exploited?
What is the CVSS score of CVE-2026-100872?
How do I remediate CVE-2026-100872?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-100872
Is Your Infrastructure Affected by CVE-2026-100872?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.