Skip to content
Fencer Intel
critical 9.8

CVE-2019-8121 json

Using JS libraries with known security vulnerabilities

published 7y ago modified 4mo ago also GHSA-89ch-hqf9-rgp3 , EUVD-2019-0736

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

An insecure component vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. Magento 2 codebase leveraged outdated versions of JS libraries (Bootstrap, jquery, Knockout) with known security vulnerabilities.

Patch / fix

  • packagist magento/community-edition 2.2.10, 2.3.3
  • packagist magento/product-community-edition 2.2.10, 2.3.2-p2
  • magento magento 2.1.19, 2.2.10

Is CVE-2019-8121 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

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

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
>=2.2, <2.2.10
>=2.3, <2.3.3
2.2.10
2.3.3
packagist magento/product-community-edition
>=2.2, <2.2.10
>=2.3, <2.3.2-p2
2.2.10
2.3.2-p2

Affected products

  • Adobe Systems Incorporated Magento 2

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.