Skip to content
Fencer Intel
medium 4.4

CVE-2020-5218 json

Ability in Sylius to switch channels via GET parameter enabled in production environments

published 6y ago modified 4mo ago also CVE-2020-5220 , GHSA-8vp7-j5cj-vvm2 , GHSA-prg5-hg25-8grq , EUVD-2020-0273

cvss
4.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist sylius/sylius 1.3.12, 1.3.16, 1.4.4, 1.4.12, 1.5.9, 1.6.5
  • packagist sylius/resource-bundle 1.3.13, 1.4.6, 1.5.1, 1.6.3
  • sylius sylius 1.3.13, 1.4.6, 1.6.3

Is CVE-2020-5218 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 4.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist sylius/sylius
<1.3.16
>=1.4.0, <1.4.12
>=1.5, <1.5.9
>=1.6.0, <1.6.5
<1.3.12
>=1.4.0, <1.4.4
1.3.16
1.4.12
1.5.9
1.6.5
1.3.12
1.4.4
packagist sylius/resource-bundle
>=1.4.0, <1.4.6
>=1.5.0, <1.5.1
>=1.6.0, <1.6.3
>=1.0.0, <1.3.13
1.4.6
1.5.1
1.6.3
1.3.13

Affected products

  • Sylius Sylius

Classification

Weakness
  • CWE-444 Inconsistent Interpretation of HTTP Requests
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.