Skip to content
Fencer Intel
medium 6.5

CVE-2020-9692 json

Magento security mitigation bypass vulnerability

published 6y ago modified 2mo ago also BIT-magento-2020-9692 , EUVD-2022-5410 , GHSA-vqg7-8v6x-54rq

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

Summary

Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have a security mitigation bypass vulnerability. Successful exploitation could lead to arbitrary code execution.

Patch / fix

  • packagist magento/community-edition 2.3.5-p2
  • bitnami magento 2.3.5
  • magento magento 2.3.5

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

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

CVSS scores

assigned by version score vector
GitHub 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 8.5 AV:N/AC:M/Au:S/C:C/I:C/A:C
OSV 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
<2.3.5-p2
2.3.5-p2
bitnami magento
<2.3.5
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.