{"id":"CVE-2026-53639","summary":"Sylius: IDOR on Shop Payment Request API endpoints","details":"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.","aliases":["GHSA-mr9r-h354-966r"],"modified":"2026-09-11T03:31:01.303758413Z","published":"2026-09-08T22:22:24.578Z","database_specific":{"cwe_ids":["CWE-639"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53639.json","cna_assigner":"GitHub_M"},"references":[{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53639.json"},{"type":"ADVISORY","url":"https://github.com/Sylius/Sylius/security/advisories/GHSA-mr9r-h354-966r"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53639"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/sylius/sylius","events":[{"introduced":"6dd3ca9895be7ab7e6cb71f37af2ef66af17cbe0"},{"fixed":"45f70193ea0e83826ec72af4a92c806616539e71"},{"introduced":"a5a816f9f1fcb5abd2d42b27801656aa2ae9bf0d"},{"fixed":"894f29731765b1c1249ba73eb9df36c998f962ce"},{"introduced":"7aa47be3a617f75337d73d245352ea700bc8a1ef"},{"fixed":"a1a074a079bd023e211cbf226b2ca25f05e7bd0c"}],"database_specific":{"extracted_events":[{"introduced":"2.0.0"},{"fixed":"2.0.18"},{"introduced":"2.1.0"},{"fixed":"2.1.15"},{"introduced":"2.2.0"},{"fixed":"2.2.6"}],"source":"AFFECTED_FIELD"}}],"versions":["v2.2.5","v2.1.14","v2.2.4","v2.1.13","v2.0.17","v2.2.3","v2.1.12","v2.0.16","v2.2.2","v2.1.11","v2.2.1","v2.1.10","v2.0.15","v2.2.0","v2.1.9","v2.0.14","v2.1.8","v2.1.7","v2.1.6","v2.1.5","v2.0.13","v2.1.4","v2.0.12","v2.1.3","v2.0.11","v2.1.2","v2.0.10","v2.1.1","v2.0.9","v2.1.0","v2.0.8","v2.0.7","v2.0.6","v2.0.5","v2.0.4","v2.0.3","v2.0.2","v2.0.1","v2.0.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53639.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V4","score":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"}]}