{"answers":{"affected":"6 open source packages ship an affected version, including sylius/sylius.","exploited":"There is no known exploitation of CVE-2026-53639 in the wild and no public exploit code.","fix":"Upgrade sylius/sylius to a fixed version for your release line: 2.0.18, 2.1.15 or 2.2.6.","what":"CVE-2026-53639 is a medium-severity missing authorization vulnerability in Sylius, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53639 and fix it if it is affected.\n\nWhat it is: CVE-2026-53639 is a medium-severity missing authorization vulnerability in Sylius, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53639 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sylius/sylius (Packagist): affected from 2.0.0; fixed in 2.0.18\n- sylius/sylius (Packagist): affected from 2.0.0; fixed in 2.0.18\n- sylius/sylius (Packagist): affected from 2.1.0; fixed in 2.1.15\n- sylius/sylius (Packagist): affected from 2.1.0; fixed in 2.1.15\n- sylius/sylius (Packagist): affected from 2.2.0; fixed in 2.2.6\n- sylius/sylius (Packagist): affected from 2.2.0; fixed in 2.2.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53639/ (Markdown: https://insights.sbomify.com/CVE-2026-53639/index.md)","id":"CVE-2026-53639","markdown":"https://insights.sbomify.com/CVE-2026-53639/index.md","name":"CVE-2026-53639","record":{"aliases":["GHSA-mr9r-h354-966r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Sylius eCommerce Framework","requires_auth":"none","summary":"Attackers with a payment request hash can read order details and modify redirect URLs due to missing ownership checks in Sylius API endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Sylius: IDOR on Shop Payment Request API endpoints","id":"CVE-2026-53639","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":6,"n_references":1,"next":{"headline":"Missing authorization in FOSSBilling","id":"CVE-2026-53640"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.18"],"introduced":["2.0.0"],"last_affected":[],"package":"sylius/sylius","purl":null,"source":"GHSA-mr9r-h354-966r"},{"ecosystem":"Packagist","fixed":["2.0.18"],"introduced":["2.0.0"],"last_affected":[],"package":"sylius/sylius","purl":"pkg:composer/sylius/sylius","source":"GHSA-mr9r-h354-966r"},{"ecosystem":"Packagist","fixed":["2.1.15"],"introduced":["2.1.0"],"last_affected":[],"package":"sylius/sylius","purl":null,"source":"GHSA-mr9r-h354-966r"},{"ecosystem":"Packagist","fixed":["2.1.15"],"introduced":["2.1.0"],"last_affected":[],"package":"sylius/sylius","purl":"pkg:composer/sylius/sylius","source":"GHSA-mr9r-h354-966r"},{"ecosystem":"Packagist","fixed":["2.2.6"],"introduced":["2.2.0"],"last_affected":[],"package":"sylius/sylius","purl":null,"source":"GHSA-mr9r-h354-966r"},{"ecosystem":"Packagist","fixed":["2.2.6"],"introduced":["2.2.0"],"last_affected":[],"package":"sylius/sylius","purl":"pkg:composer/sylius/sylius","source":"GHSA-mr9r-h354-966r"}],"prev":{"headline":"Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint","id":"CVE-2026-53638"},"products":["Sylius"],"published":"2026-09-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-09","vendors":["Sylius"]},"summary":"Attackers with a payment request hash can read order details and modify redirect URLs due to missing ownership checks in Sylius API endpoints.","url":"https://insights.sbomify.com/CVE-2026-53639/"}