Skip to content
Fencer Intel
critical 9.8

CVE-2020-9580 json

Magento Security mitigation bypass vulnerability

published 6y ago modified 2mo ago also BIT-magento-2020-9580 , EUVD-2022-4260 , GHSA-j2jp-58gv-g2pg

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

Summary

Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a security mitigation bypass vulnerability. Successful exploitation could lead to arbitrary code execution.

Patch / fix

  • packagist magento/community-edition 2.3.4-p2
  • packagist magento/core 1.9.4.5
  • bitnami magento 2.2.12, 2.3.5

Is CVE-2020-9580 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

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

CVSS scores

assigned by version score vector
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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
OSV 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.2.11
>=2.3.0, <2.3.4-p2
2.3.4-p2
packagist magento/core
<1.9.4.5
1.9.4.5
packagist magento/project-community-edition
<=2.0.2
 no fix listed
bitnami magento
>=2.2.0, <2.2.12
>=2.3.0, <2.3.5
2.2.12
2.3.5

Affected products

  • Adobe Magento

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.