CVE-2019-12186 — sylius/grid
MEDIUMCVE-2019-12186 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in sylius/grid. A fix is available for sylius/grid — see the affected versions and patch details below.
XSS injection in the Grid component of Sylius
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2019-12186 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
sylius/grid🐘sylius/grid🐘sylius/grid🐘sylius/grid🐘sylius/grid🐘sylius/grid-bundle🐘sylius/grid-bundle🐘sylius/grid-bundle+6 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in Sylius products. Missing input sanitization in sylius/sylius 1.0.x through 1.0.18, 1.1.x through 1.1.17, 1.2.x through 1.2.16, 1.3.x through 1.3.11, and 1.4.x through 1.4.3 and sylius/grid 1.0.x through 1.0.18, 1.1.x through 1.1.18, 1.2.x through 1.2.17, 1.3.x through 1.3.12, 1.4.x through 1.4.4, and 1.5.0 allows an attacker (an admin in the sylius/sylius case) to perform XSS by injecting malicious code into a field displayed in a grid with the "string" field type. The contents are an object, with malicious code returned by the __toString() method of that object.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | sylius/grid | ≥ 1.0.0&&< 1.1.19 | 1.1.19composer require sylius/grid:^1.1.19 |
| 🐘Packagist | sylius/grid | ≥ 1.2.0&&< 1.2.18 | 1.2.18composer require sylius/grid:^1.2.18 |
| 🐘Packagist | sylius/grid | ≥ 1.3.0&&< 1.3.13 | 1.3.13composer require sylius/grid:^1.3.13 |
| 🐘Packagist | sylius/grid | ≥ 1.4.0&&< 1.4.5 | 1.4.5composer require sylius/grid:^1.4.5 |
| 🐘Packagist | sylius/grid | ≥ 1.5.0&&< 1.5.1 | 1.5.1composer require sylius/grid:^1.5.1 |
| 🐘Packagist | sylius/grid-bundle | ≥ 1.0.0&&< 1.1.19 | 1.1.19composer require sylius/grid-bundle:^1.1.19 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sylius/grid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sylius/grid to 1.1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12186 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-12186 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-12186. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-12186 in your dependencies?
O3 Security finds CVE-2019-12186 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.