CVE-2026-100869

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-09-27. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Sylius versions before 2.1.16 and 2.2.9 fail to restrict payment request actions in the Shop API endpoint, allowing customers to trigger refunds on completed orders. Attackers with order tokens can submit arbitrary payment actions like refunds that payment gateways execute while Sylius maintains order as paid, causing financial loss.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
27
EG Risk 27/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 computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
generic

Sylius 2.x before 2.1.16 and 2.2.9 Arbitrary Payment Action via Shop API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sylius-2-x-before-2.1.16-and-2.2.9-arbitrary-payment-action-via-shop-api
github Patch Available

Shop API accepts arbitrary PaymentRequest actions, allowing a customer-triggered refund · Advisory · Sylius/Sylius · GitHub

Affected: versions: 2.1.16, 2.2.9 and above.

https://github.com/Sylius/Sylius/security/advisories/GHSA-2rv4-pjmm-7fxf
github_release Patch Available

v2.2.9

Patch available: Sylius/Sylius v2.2.9

https://github.com/Sylius/Sylius/releases/tag/v2.2.9
github_pr Patch Available

[2.2][ApiBundle] Restrict PaymentRequest actions allowed from shop context

Patch available: Sylius/Sylius v2.2.9 (PR #19214 merged 2026-09-02)

https://github.com/Sylius/Sylius/pull/19214
github_commit Patch Available

commit 5813831f60f3 (Sylius/Sylius)

Patch available: Sylius/Sylius v2.2.9 (contains commit 5813831f60f3)

https://github.com/Sylius/Sylius/commit/5813831f60f3a60b735a86a57c4b519626a3b75d
generic

GitHub - Sylius/Sylius: Headless open-source eCommerce platform on top of PHP/Symfony/API Platform · GitHub

https://github.com/Sylius/Sylius

Vendor Advisories for CVE-2026-100869(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 21× in last 7d / 24× 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.

  1. 2026-10-04 02:43 UTCEG score recompute
  2. 2026-10-04 02:43 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 01:59 UTCEG score recompute
  5. 2026-10-03 01:59 UTCGHSA enrichment
  6. 2026-10-02 01:16 UTCEG score recompute
  7. 2026-10-02 01:16 UTCGHSA enrichment
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-10-01 00:33 UTCEG score recompute
  10. 2026-10-01 00:33 UTCGHSA enrichment
  11. 2026-09-30 15:02 UTCEPSS rescore
  12. 2026-09-29 23:47 UTCEG score recompute
  13. 2026-09-29 23:47 UTCGHSA enrichment
  14. 2026-09-29 15:20 UTCEPSS rescore
  15. 2026-09-28 21:13 UTCGHSA enrichment
  16. 2026-09-28 14:26 UTCEG score recompute
  17. 2026-09-28 14:26 UTCGHSA enrichment
  18. 2026-09-28 13:50 UTCEPSS rescore
  19. 2026-09-28 13:27 UTCEG score recompute
  20. 2026-09-28 13:27 UTCGHSA enrichment
  21. 2026-09-27 14:35 UTCEG score recompute
  22. 2026-09-27 13:18 UTCEG score recompute
  23. 2026-09-27 13:16 UTCEG score recompute
  24. 2026-09-27 13:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-100869?
CVE-2026-100869 is a medium vulnerability published on September 27, 2026. Sylius versions before 2.1.16 and 2.2.9 fail to restrict payment request actions in the Shop API endpoint, allowing customers to trigger refunds on completed orders. Attackers with order tokens can submit arbitrary payment actions like refunds that payment gateways execute while Sylius maintains…
When was CVE-2026-100869 disclosed?
CVE-2026-100869 was first published on September 27, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100869 actively exploited?
CVE-2026-100869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100869?
CVE-2026-100869 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100869?
A fix for CVE-2026-100869 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100869 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100869

Explore →

Is Your Infrastructure Affected by CVE-2026-100869?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.