Magento 2 Community Edition RCE Vulnerability

published 2019-11-05 7y ago modified 2026-06-17 4mo ago also GHSA-vpg9-gq7j-mxqg , EUVD-2022-5394

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

A remote code execution vulnerability exists in Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An unauthenticated user can insert a malicious payload through PageBuilder template methods.

Patch / fix

fixed in 2 links 1

packagist magento/community-edition 2.3.2-p1
magento magento 2.3.2

magento.com/security/patches/magento-2.3.3-and-2.2.10-security-update advisory

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

2.76% chance of exploitation in the next 30 days, higher than 86% 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
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	magento/community-edition	>=2.3, <2.3.2-p1	2.3.2-p1

Affected products

Adobe Systems Incorporated Magento 2

References

Sources

CVE List CVE-2019-8144
GitHub Advisory GHSA-vpg9-gq7j-mxqg
NVD CVE-2019-8144

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.