How severe is CVE-2019-12186?

CVE-2019-12186 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-12186?

CVE-2019-12186 affects the following packages: sylius/grid (Packagist), sylius/grid (Packagist), sylius/grid (Packagist), sylius/grid (Packagist), sylius/grid (Packagist), sylius/grid-bundle (Packagist), sylius/grid-bundle (Packagist), sylius/grid-bundle (Packagist), and 6 more. Ecosystems affected: Packagist.

How do I fix CVE-2019-12186?

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.

How do I detect CVE-2019-12186 in my Packagist dependencies?

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.

How do I mitigate CVE-2019-12186 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2019-12186 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-12186 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-12186?

CVE-2019-12186 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-12186?

CVE-2019-12186 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-12186 published, and has it been updated?

CVE-2019-12186 was published on December 31, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2019-12186 — grid

MEDIUM

CVE-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

Also known asGHSA-rc5r-697f-28x6

Published

Dec 31, 2019

Updated

Oct 24, 2026

Affected

14 pkgs

Patched

14 / 14

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

14 pkgs affected

🐘sylius/grid🐘sylius/grid🐘sylius/grid🐘sylius/grid🐘sylius/grid🐘sylius/grid-bundle🐘sylius/grid-bundle🐘sylius/grid-bundle+6 more

Real-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

14 total 14 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`sylius/grid`	≥ 1.0.0&&< 1.1.19	1.1.19`composer require sylius/grid:^1.1.19`
🐘Packagist	`sylius/grid`	≥ 1.2.0&&< 1.2.18	1.2.18`composer require sylius/grid:^1.2.18`
🐘Packagist	`sylius/grid`	≥ 1.3.0&&< 1.3.13	1.3.13`composer require sylius/grid:^1.3.13`
🐘Packagist	`sylius/grid`	≥ 1.4.0&&< 1.4.5	1.4.5`composer require sylius/grid:^1.4.5`
🐘Packagist	`sylius/grid`	≥ 1.5.0&&< 1.5.1	1.5.1`composer require sylius/grid:^1.5.1`
🐘Packagist	`sylius/grid-bundle`	≥ 1.0.0&&< 1.1.19	1.1.19`composer require sylius/grid-bundle:^1.1.19`

Affected Products

2 products · 11 configurations

Application

gridsylius

≥ 1.4.0 && ≤ 1.4.4

1 version

1.5.0

Application

syliussylius

≥ 1.4.0 && ≤ 1.4.3

range

Detection & mitigation playbook

Open-source dependency

Detect
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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-12186 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

security-advisories

4.8/10

Maintained10/10

Code-Review10/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Dec 31, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-12186

GHSA-rc5r-697f-28x6

References

Advisorysylius.com · cve 2019 12186 Advisorynvd.nist.gov · CVE 2019 12186 Webgithub.com · CVE 2019 12186.yaml Webgithub.com · CVE 2019 12186.yaml Websylius.com · cve 2019 12186

Related vulnerabilities

Also affects sylius/grid-bundle

This CVE is medium severity; 1 of 1 other CVE affecting sylius/grid-bundle is rated as high or higher (top: critical).

CVE-2022-24752

Also affects sylius/sylius

This CVE is medium severity; 7 of 7 other CVEs affecting sylius/sylius are rated as high or higher (top: high).

CVE-2026-53637CVE-2026-53638CVE-2026-53639CVE-2026-31820CVE-2026-31824CVE-2026-31819CVE-2026-31823

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026