Skip to content
Fencer Intel
high 7.2

CVE-2019-7896 json

Magento 2 Community Edition RCE Vulnerability

published 7y ago modified 4mo ago also GHSA-2x55-mg9r-24f7 , EUVD-2022-2069

cvss
7.2
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

A remote code execution vulnerability exists in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. An authenticated user with administrator privileges to layouts can execute arbitrary code through a combination of product import, crafted csv file and XML layout update.

Patch / fix

  • packagist magento/community-edition 2.1.18, 2.2.9, 2.3.2
  • magento magento 2.1.18, 2.2.9, 2.3.2

Is CVE-2019-7896 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.92% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.2 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.0 7.2 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
>=2.1, <2.1.18
>=2.2, <2.2.9
>=2.3, <2.3.2
2.1.18
2.2.9
2.3.2

Affected products

  • n/a 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.