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

Back
New CVE Detected

CVE-2026-100869 – Incorrect Authorization (Unauthorized Refund/Payment Actions) – Sylius 2.0.0–2.1.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100869 is an incorrect-authorization vulnerability in the Sylius e-commerce platform’s Shop API. The POST /api/v2/shop/orders/{tokenValue}/payment-requests endpoint fails to restrict which payment request actions a customer may submit, allowing a customer who holds a valid order token to trigger unauthorized payment actions — such as refunds — on their own completed orders. The issue is rated HIGH severity under CVSS v4.0 (8.2) and MEDIUM under CVSS v3.1 (5.9), and can cause direct financial loss to merchants.

Technical details

  • Root cause: The Shop API payment-requests endpoint validates only that the requester owns the order (via the order token) but does not restrict or authorize the specific payment "action" value being submitted, per CWE-863 (Incorrect Authorization).
  • Trigger conditions: The Shop API must be enabled and reachable, the order must already be completed/paid, and the store’s configured payment gateway must implement a refund-class (or similarly sensitive) payment action that the API can invoke.
  • Attack vector: Network-based; an attacker only needs a valid order token (obtainable as the legitimate customer of that order) to submit arbitrary payment action requests — no elevated privileges or user interaction beyond that are required.
  • Impact: Attackers can cause the configured payment gateway to execute actions like refunds while Sylius continues to record the order internally as paid, producing a mismatch that results in financial loss to the merchant. The impact is limited to integrity (order/payment state); confidentiality and availability are not affected.

Affected software

  • Sylius/Sylius (sylius/sylius on Packagist): versions 2.0.0 up to but not including 2.1.16
  • Sylius/Sylius: versions 2.2.0 up to but not including 2.2.9

Severity

  • CVSS v3.1 Base Score: 5.9 (Medium) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
  • CVSS v4.0 Base Score: 8.2 (High) — CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
  • CWE-863: Incorrect Authorization

Mitigation and recommended actions

  • Immediate: Upgrade to Sylius 2.1.16 or 2.2.9 (or later), which restrict the payment request actions permitted through the Shop API endpoint.
  • If no patch can be applied immediately: Restrict or disable public exposure of the Shop API’s payment-requests endpoint where not required, review configured payment gateways for refund-class actions reachable via this endpoint, and monitor for unexpected refund or payment-state-change activity on completed orders as a compensating control until the upgrade is 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