Skip to content
Fencer Intel
high 7.2

CVE-2020-9588 json

Magento Signature verification bypass

published 6y ago modified 2mo ago also BIT-magento-2020-9588 , EUVD-2022-4261 , GHSA-j2r4-2cr6-h3r3

cvss
7.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 87%
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 an observable timing discrepancy vulnerability. Successful exploitation could lead to signature verification bypass.

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

CVSS scores

assigned by version score vector
GitHub 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
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/community-edition
<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

Classification

Weakness

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.