Skip to content
Fencer Intel
critical 9.8

CVE-2020-3716 in the critical feed json

Magento deserialization vulnerability

published 6y ago modified 2mo ago also BIT-magento-2020-3716 , EUVD-2022-3454 , GHSA-9wc9-498w-h8xv

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

Summary

Magento versions 2.3.3 and earlier, 2.2.10 and earlier, 1.14.4.3 and earlier, and 1.9.4.3 and earlier have a deserialization of untrusted data vulnerability. Successful exploitation could lead to arbitrary code execution.

Patch / fix

  • packagist magento/community-edition 2.2.11, 2.3.4
  • bitnami magento 2.2.11, 2.3.4

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

13.96% chance of exploitation in the next 30 days, higher than 96% 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 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C
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.0, <2.2.11
>=2.3.0, <2.3.4
2.2.11
2.3.4
bitnami magento
>=2.2.0, <2.2.11
>=2.3.0, <2.3.4
2.2.11
2.3.4

Affected products

  • Adobe Magento

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

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.