CVE-2020-5218

Workarounds

Unsupported versions could be patched by adding the following configuration to run in production:

sylius_channel:
    debug: false

This vulnerability gives 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.

CVE-2020-5218 has a CVSS score of 4.4 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.16, 1.4.12, 1.5.9, 1.6.5); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2020-5218? CVE-2020-5218 is a low-severity security vulnerability in sylius/sylius (composer), affecting versions < 1.3.16. It is fixed in 1.3.16, 1.4.12, 1.5.9, 1.6.5.
2. How severe is CVE-2020-5218? CVE-2020-5218 has a CVSS score of 4.4 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of sylius/sylius are affected by CVE-2020-5218? sylius/sylius (composer) versions < 1.3.16 is affected.
4. Is there a fix for CVE-2020-5218? Yes. CVE-2020-5218 is fixed in 1.3.16, 1.4.12, 1.5.9, 1.6.5. Upgrade to this version or later.
5. Is CVE-2020-5218 exploitable, and should I be worried? Whether CVE-2020-5218 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2020-5218 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2020-5218?
   • Upgrade sylius/sylius to 1.3.16 or later
   • Upgrade sylius/sylius to 1.4.12 or later
   • Upgrade sylius/sylius to 1.5.9 or later
   • Upgrade sylius/sylius to 1.6.5 or later

Other vulnerabilities in sylius/sylius