← console
voxell vciy

CVE-2021-28566: Magento Commerce information disclosure during upload action leveraging a specially crafted file

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. No fix version is held. The CNA's first reference is the place to look: helpx.adobe.com
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

Magento versions 2.4.2 (and earlier), 2.4.1-p1 (and earlier) and 2.3.6-p1 (and earlier) are vulnerable to an Information Disclosure vulnerability when uploading a modified png file to a product image. Successful exploitation could lead to the disclosure of document root path by an unauthenticated attacker. Access to the admin console is required for successful exploitation.

weakness
CWE-200 Information Exposure (CWE-200)
affected
Adobe Magento Commerce
published ranges
magento <= 2.4.2
fixed in
No fix version in held sources.
fixed by package (from OSV advisories)
magento (Bitnami): 2.4.3 BIT-magento-2021-28566magento/community-edition (Packagist): 2.3.7; 2.4.2-p1 GHSA-w942-fw92-mqm2
later fixes (from OSV advisories)
magento 2.4.3 is inside a range CVE-2022-42344 (BIT-magento-2022-42344) lists as affected. That advisory is fixed in 2.4.5.magento 2.4.3 is inside a range CVE-2024-45124 (BIT-magento-2024-45124) lists as affected. That advisory is fixed in 2.4.4-p11.magento 2.4.3 is inside a range CVE-2024-45125 (BIT-magento-2024-45125) lists as affected. That advisory is fixed in 2.4.4-p11.magento 2.4.3 is inside a range CVE-2024-45127 (BIT-magento-2024-45127) lists as affected. That advisory is fixed in 2.4.4-p11.magento 2.4.3 is inside a range CVE-2024-45128 (BIT-magento-2024-45128) lists as affected. That advisory is fixed in 2.4.4-p11.magento 2.4.3 is inside a range CVE-2024-45129 (BIT-magento-2024-45129) lists as affected. That advisory is fixed in 2.4.4-p11.
severity
3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
assigned by
adobe
published
2021-09-08

check us helpx.adobe.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
9 Sep 20210.00416
6 Jan 20220.0184
4 Feb 20220.04499
1 Apr 20220.00885
7 Mar 20230.00063scoring model v2023.03.01
8 Mar 20230.00063
17 Mar 20250.00873scoring model v2025.03.14
19 Mar 20250.00837
29 Mar 20250.01872
30 Mar 20250.00837
19 Oct 20250.00731
12 Jan 20260.00539
16 Apr 20260.00731
15 Jun 20260.01379scoring model v2026.06.15
2 Jul 20260.01425

15 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-07-02 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
No fix version is held. One published by the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-28566', '2026-10-31T23:59:59.999999Z', now());