{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5218 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-5218 is a medium-severity vulnerability in Sylius, published on 27 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-5218 and fix it if it is affected.\n\nWhat it is: CVE-2020-5218 is a medium-severity vulnerability in Sylius, published on 27 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-5218 in the wild and no public exploit code.\n\nAffected product: Sylius. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2020-5218/ (Markdown: https://insights.sbomify.com/CVE-2020-5218/index.md)","id":"CVE-2020-5218","markdown":"https://insights.sbomify.com/CVE-2020-5218/index.md","name":"CVE-2020-5218","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Sylius e-commerce platform","requires_auth":"low_privilege","summary":"Attackers can bypass production security restrictions to switch channels via GET parameters due to a configuration resolution bug in Sylius.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sylius","vendor":"sylius"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"Affected versions of Sylius give attackers the ability to switch channels via the _channel_code GET parameter in production environments. This was meant to be enabled only when kernel.debug is set to true. However, if no sylius_channel.debug is set explicitly in the configuration, the default value which is kernel.debug will be not resolved and cast to boolean, enabling this debug feature even if that parameter is set to false. Patch has been provided for Sylius 1.3.x and newer - 1.3.16, 1.4.12, 1.5.9, 1.6.5. Versions older than 1.3 are not covered by our security support anymore.","ecosystems":[],"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":"Ability in Sylius to switch channels via GET parameter enabled in production environments","id":"CVE-2020-5218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Remote Code Execution in Angular Expressions","id":"CVE-2020-5219"},"packages":[],"prev":{"headline":"Directive injection when using dynamic overrides with user input in RubyGems secure_headers","id":"CVE-2020-5217"},"products":["Sylius"],"published":"2020-01-27","related":[{"cvss_score":8.2,"headline":"Sylius has a Promotion Usage Limit Bypass via Race Condition","id":"CVE-2026-31824","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-57610","kev_date_added":null,"published":"2025-02-06"},{"cvss_score":7.1,"headline":"Sylius affected by IDOR in Cart and Checkout LiveComponents","id":"CVE-2026-31820","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.1,"headline":"Insufficient Session Expiration in Sylius","id":"CVE-2022-24743","kev_date_added":null,"published":"2022-03-14"},{"cvss_score":6.9,"headline":"Sylius has an Open Redirect via Referer Header","id":"CVE-2026-31819","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.9,"headline":"Sylius is Missing Authorization in API v2 Add Item Endpoint","id":"CVE-2026-31821","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.4,"headline":"Sylius has potential Cross Site Scripting vulnerability via the \"Province\" field in the Checkout and Address Book","id":"CVE-2024-29376","kev_date_added":null,"published":"2024-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Sylius"]},"summary":"Attackers can bypass production security restrictions to switch channels via GET parameters due to a configuration resolution bug in Sylius.","url":"https://insights.sbomify.com/CVE-2020-5218/"}