CVE-2026-53639

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Sylius is an Open Source eCommerce Framework on Symfony. Starting in version 2.0.0 and prior to version 2.0.18, 2.1.15, and 2.2.6, the GET /api/v2/shop/payment-requests/{hash} and PUT /api/v2/shop/payment-requests/{hash} endpoints look up the payment request solely by the hash from the URL. No ownership check is performed against the authenticated customer or the underlying order. An attacker who obtains a payment request hash can read the payment request and, through the payment IRI in the response, recover the underlying order's tokenValue (which itself grants access to the full order, items, addresses, customer email, totals); and/or update the payment request payload (e.g. target_path, after_path). These fields are used by the front-end controller to redirect the user after the payment, so an attacker can flip them to an attacker-controlled URL and intercept the buyer. The hash is a UUID, so it has to be obtained out-of-band (logs, shared links, referrer headers, a co-located client), but once it is known no other credential is required, neither authentication nor knowledge of the order token. The creation endpoint POST /api/v2/shop/orders/{tokenValue}/payment-requests shares the same flaw: it resolves the target order solely from the tokenValue in the URL without verifying that the caller owns the order. The issue is fixed in versions 2.0.18, 2.1.15, and 2.2.6. As a workaround, add a query extension that filters the GET operation; decorate the PUT state provider, guard the POST creation endpoint with a command-bus middleware, and wire the services.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

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 (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 9, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

IDOR on Shop Payment Request endpoints in API · Advisory · Sylius/Sylius · GitHub

Affected: versions: 2.0.18, 2.1.15, 2.2.6.

https://github.com/Sylius/Sylius/security/advisories/GHSA-mr9r-h354-966r

Vendor Advisories for CVE-2026-53639(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
sylius/syliusv2.2.0 ... v2.2.5 (6 versions)
  • 2.0.0 up to 2.0.18: fixed in 2.0.18
  • 2.1.0 up to 2.1.15: fixed in 2.1.15
  • 2.2.0 up to 2.2.6: fixed in 2.2.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-12 15:57 UTCEG score recompute
  4. 2026-10-11 19:40 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-01 16:00 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-09-28 10:02 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 23 more
  1. 2026-09-24 11:23 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-09-23 05:53 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-09-18 05:34 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-09-14 06:47 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-09-13 08:17 UTCEG score recompute
  12. 2026-09-12 03:21 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-09-09 17:34 UTCEG score recompute
  16. 2026-09-09 16:55 UTCEG score recompute
  17. 2026-09-08 23:21 UTCEG score recompute
  18. 2026-09-08 22:31 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  19. 2026-09-08 22:28 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  20. 2026-08-02 04:14 UTCEG score recompute
  21. 2026-07-26 12:16 UTCEG score recompute
  22. 2026-07-23 03:19 UTCEG score recompute
  23. 2026-07-09 21:46 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-53639?
CVE-2026-53639 is a medium-severity vulnerability; its CVE record was published on July 9, 2026. Sylius is an Open Source eCommerce Framework on Symfony. Starting in version 2.0.0 and prior to version 2.0.18, 2.1.15, and 2.2.6, the GET /api/v2/shop/payment-requests/{hash} and PUT /api/v2/shop/payment-requests/{hash} endpoints look up the payment request solely by the hash from the URL. No…
When was the CVE record for CVE-2026-53639 published?
The CVE record for CVE-2026-53639 was published on July 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-53639 actively exploited?
CVE-2026-53639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53639?
CVE-2026-53639 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53639?
A fix for CVE-2026-53639 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53639 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53639

Explore →

Is Your Infrastructure Affected by CVE-2026-53639?

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

Book a Demo →Browse All CVEs