Skip to content
Fencer Intel
critical 9.1

CVE-2021-36023 json

Magento Commerce Widgets Update Layout XML Injection Vulnerability Could Lead To Remote Code Execution

published 3y ago modified last mo. also BIT-magento-2021-36023 , EUVD-2021-22656 , GHSA-8cjg-f53m-8m9q

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an XML Injection vulnerability in the Widgets Update Layout. An attacker with admin privileges can trigger a specially crafted script to achieve remote code execution.

Patch / fix

  • packagist magento/community-edition 2.3.7-p1, 2.4.2-p2
  • bitnami magento 2.3.7, 2.4.2
  • magento magento 2.3.7, 2.4.2

Is CVE-2021-36023 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist magento/project-community-edition
<=2.0.2
no fix listed
packagist magento/community-edition
<2.3.7-p1
1 listed version
>=2.4.2-p1, <2.4.2-p2
2.3.7-p1
2.4.2-p2
bitnami magento
<2.3.7
>=2.4.0, <2.4.2
2.3.7
2.4.2

Affected products

  • Adobe Adobe Commerce

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

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.