Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-100872 – Payment Amount Manipulation / Order Fraud – Sylius 2.0.0–2.1.15 and 2.2.0–2.2.8

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100872 is a payment/order-integrity vulnerability in Sylius, the open-source e-commerce platform, caused by insufficient verification of payment amounts during cart recalculation. Unauthenticated attackers can pay a small amount through a payment gateway and then inflate the order total afterward, causing Sylius to mark the larger order as fully paid even though the gateway only captured the original, smaller amount. The issue is rated HIGH severity (CVSS 8.7).

Technical details

  • Root cause: Sylius fails to validate that the amount confirmed by the payment gateway matches the current order/payment total when a cart is recalculated after a gateway transaction has already been initiated (CWE-345, Insufficient Verification of Data Authenticity).
  • Trigger conditions: A guest or customer initiates checkout on a Sylius 2.x store using a capture-capable Payum gateway and the Payment Request API, starts a gateway capture for a low-value cart, and then triggers a cart recalculation that overwrites the existing local payment record with an enlarged order total.
  • Attack vector: Network-based, low attack complexity, no privileges required, no user interaction beyond normal checkout steps — exploitable by any unauthenticated visitor able to reach the storefront checkout flow.
  • Impact: Sylius completes the rewritten, higher-value payment without re-verifying the amount actually captured by the gateway, allowing the attacker to obtain goods/services priced above what was actually paid (underpayment/order-total fraud). Confidentiality and system availability are not affected; the impact is limited to payment/order integrity.

Affected software

  • Sylius (sylius/sylius Composer package) versions 2.0.0 through 2.1.15
  • Sylius (sylius/sylius Composer package) versions 2.2.0 through 2.2.8

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
  • CVSS v4.0 Score: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Sylius to version 2.1.16 or 2.2.9 (or later), which prevent claimed payments from being rewritten or removed after a gateway capture has been confirmed.
  • If no patch: Where upgrading is not immediately possible, closely monitor and reconcile completed orders against actual amounts captured by the payment gateway, and consider disabling or restricting cart recalculation after a payment capture has been initiated until the patch can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge