Skip to content
Fencer Intel
high 7.2

CVE-2021-36021 json

Magento Commerce CMS Page Improper Input Validation Could Lead To Remote Code Execution

published 3y ago modified 2mo ago also BIT-magento-2021-36021 , EUVD-2021-22654 , GHSA-4g27-q2w9-m8m8

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

Summary

Magento versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an Improper input validation vulnerability within the CMS page scheduled update feature. An authenticated attacker with administrative privilege could leverage this vulnerability to achieve remote code execution on the system.

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-36021 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
2y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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
OSV 3.1 7.2 CVSS:3.1/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/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-20 Improper Input Validation

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.