What is CVE-2019-12186?

CVE-2019-12186 is a medium-severity cross-site scripting (XSS) vulnerability in sylius/grid (composer), affecting versions >= 1.0.0, < 1.1.19. It is fixed in 1.1.19, 1.2.18, 1.3.13, 1.4.5, 1.5.1, 1.1.18, 1.2.17, 1.3.12, 1.4.4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2019-12186?

CVE-2019-12186 has a CVSS score of 4.8 (Medium). 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.

Which packages are affected by CVE-2019-12186?

sylius/grid (composer) versions >= 1.0.0, = 1.0.0, = 1.0.0, < 1.1.18.

Is there a fix for CVE-2019-12186?

Yes. CVE-2019-12186 is fixed in 1.1.19, 1.2.18, 1.3.13, 1.4.5, 1.5.1, 1.1.18, 1.2.17, 1.3.12, 1.4.4. Upgrade to this version or later.

Is CVE-2019-12186 exploitable, and should I be worried?

Whether CVE-2019-12186 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.

What actually determines whether CVE-2019-12186 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.

CVE-2019-12186 in sylius/grid | Intelligent Application Security

Q: How severe is CVE-2019-12186?

CVE-2019-12186 has a CVSS score of 4.8 (Medium). 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.

Q: Which packages are affected by CVE-2019-12186?

sylius/grid (composer) versions >= 1.0.0, = 1.0.0, = 1.0.0, < 1.1.18.

Q: Is there a fix for CVE-2019-12186?

Yes. CVE-2019-12186 is fixed in 1.1.19, 1.2.18, 1.3.13, 1.4.5, 1.5.1, 1.1.18, 1.2.17, 1.3.12, 1.4.4. Upgrade to this version or later.

Q: Is CVE-2019-12186 exploitable, and should I be worried?

Whether CVE-2019-12186 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.

Q: What actually determines whether CVE-2019-12186 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.

Q: How do I fix CVE-2019-12186?

Upgrade: sylius/grid to 1.1.19 or later, sylius/grid to 1.2.18 or later, sylius/grid to 1.3.13 or later, sylius/grid to 1.4.5 or later, sylius/grid to 1.5.1 or later, sylius/grid-bundle to 1.1.19 or later, sylius/grid-bundle to 1.2.18 or later, sylius/grid-bundle to 1.3.13 or later, sylius/grid-bundle to 1.4.5 or later, sylius/grid-bundle to 1.5.1 or later, sylius/sylius to 1.1.18 or later, sylius/sylius to 1.2.17 or later, sylius/sylius to 1.3.12 or later, sylius/sylius to 1.4.4 or later.

Summary

Grid component of Sylius omits HTML input sanitisation while rendering object implementing __toString() method through the string field type.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2019-12186 has a CVSS score of 4.8 (Medium). The vector is network-reachable, high 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.1.19, 1.2.18, 1.3.13, 1.4.5, 1.5.1, 1.1.18, 1.2.17, 1.3.12, 1.4.4); upgrading removes the vulnerable code path.

Affected versions

sylius/grid (>= 1.0.0, < 1.1.19) sylius/grid (>= 1.2.0, < 1.2.18) sylius/grid (>= 1.3.0, < 1.3.13) sylius/grid (>= 1.4.0, < 1.4.5) sylius/grid (>= 1.5.0, < 1.5.1) sylius/grid-bundle (>= 1.0.0, < 1.1.19) sylius/grid-bundle (>= 1.2.0, < 1.2.18) sylius/grid-bundle (>= 1.3.0, < 1.3.13) sylius/grid-bundle (>= 1.4.0, < 1.4.5) sylius/grid-bundle (>= 1.5.0, < 1.5.1) sylius/sylius (>= 1.0.0, < 1.1.18) sylius/sylius (>= 1.2.0, < 1.2.17) sylius/sylius (>= 1.3.0, < 1.3.12) sylius/sylius (>= 1.4.0, < 1.4.4)

Security releases

sylius/grid → 1.1.19 (composer) sylius/grid → 1.2.18 (composer) sylius/grid → 1.3.13 (composer) sylius/grid → 1.4.5 (composer) sylius/grid → 1.5.1 (composer) sylius/grid-bundle → 1.1.19 (composer) sylius/grid-bundle → 1.2.18 (composer) sylius/grid-bundle → 1.3.13 (composer) sylius/grid-bundle → 1.4.5 (composer) sylius/grid-bundle → 1.5.1 (composer) sylius/sylius → 1.1.18 (composer) sylius/sylius → 1.2.17 (composer) sylius/sylius → 1.3.12 (composer) sylius/sylius → 1.4.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

sylius/grid to 1.1.19 or later; sylius/grid to 1.2.18 or later; sylius/grid to 1.3.13 or later; sylius/grid to 1.4.5 or later; sylius/grid to 1.5.1 or later; sylius/grid-bundle to 1.1.19 or later; sylius/grid-bundle to 1.2.18 or later; sylius/grid-bundle to 1.3.13 or later; sylius/grid-bundle to 1.4.5 or later; sylius/grid-bundle to 1.5.1 or later; sylius/sylius to 1.1.18 or later; sylius/sylius to 1.2.17 or later; sylius/sylius to 1.3.12 or later; sylius/sylius to 1.4.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-12186? CVE-2019-12186 is a medium-severity cross-site scripting (XSS) vulnerability in sylius/grid (composer), affecting versions >= 1.0.0, < 1.1.19. It is fixed in 1.1.19, 1.2.18, 1.3.13, 1.4.5, 1.5.1, 1.1.18, 1.2.17, 1.3.12, 1.4.4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2019-12186? CVE-2019-12186 has a CVSS score of 4.8 (Medium). 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.
Which packages are affected by CVE-2019-12186?
- sylius/grid (composer) (versions >= 1.0.0, < 1.1.19)
- sylius/grid-bundle (composer) (versions >= 1.0.0, < 1.1.19)
- sylius/sylius (composer) (versions >= 1.0.0, < 1.1.18)
Is there a fix for CVE-2019-12186? Yes. CVE-2019-12186 is fixed in 1.1.19, 1.2.18, 1.3.13, 1.4.5, 1.5.1, 1.1.18, 1.2.17, 1.3.12, 1.4.4. Upgrade to this version or later.
Is CVE-2019-12186 exploitable, and should I be worried? Whether CVE-2019-12186 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
What actually determines whether CVE-2019-12186 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.
How do I fix CVE-2019-12186?
- Upgrade sylius/grid to 1.1.19 or later
- Upgrade sylius/grid to 1.2.18 or later
- Upgrade sylius/grid to 1.3.13 or later
- Upgrade sylius/grid to 1.4.5 or later
- Upgrade sylius/grid to 1.5.1 or later
- Upgrade sylius/grid-bundle to 1.1.19 or later
- Upgrade sylius/grid-bundle to 1.2.18 or later
- Upgrade sylius/grid-bundle to 1.3.13 or later
- Upgrade sylius/grid-bundle to 1.4.5 or later
- Upgrade sylius/grid-bundle to 1.5.1 or later
- Upgrade sylius/sylius to 1.1.18 or later
- Upgrade sylius/sylius to 1.2.17 or later
- Upgrade sylius/sylius to 1.3.12 or later
- Upgrade sylius/sylius to 1.4.4 or later