NVD / CVE Program· CNA adobe

CVE-2021-28584: Magento Commerce path traversal vulnerability in child theme store creation

HighCVSS 7.2 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 29/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 78.5% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: magento/community-edition (Packagist) 2.4.2-p1, 2.3.7.

Low priority for now. Upgrade to magento/community-edition (Packagist) 2.4.2-p1, 2.3.7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Magento versions 2.4.2 (and earlier), 2.4.1-p1 (and earlier) and 2.3.6-p1 (and earlier) are affected by a Path Traversal vulnerability when creating a store with child theme.Successful exploitation could lead to arbitrary file system write by an authenticated attacker. Access to the admin console is required for successful exploitation.

Path traversal

Published: Jun 28, 2021
Updated: Jun 16, 2026
EPSS: 1.7% · 78th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 1.7%

CNA vs NVD score

NVD: 7.2
CNA · adobe: 5.4; 1.8 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
magento	magento	cpe:2.3:a:magento:magento

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

Adobe Magento Commerce
- unspecified and later · up to and including 2.4.2affected
- unspecified and later · up to and including 2.3.6-p1affected
- unspecified and later · up to and including 2.4.1-p1affected
- unspecified and later · up to and including Noneaffected

Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

magento magentobefore 2.3.6
magento magento2.3.6
magento magento2.4.1
magento magento2.4.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist	magento/community-edition	from 2.4.0 · before 2.4.2-p1	2.4.2-p1
Packagist	magento/community-edition	before 2.3.7	2.3.7
Packagist	magento/project-community-edition	up to and including 2.0.2	—

Same product

magento: all records

Other highest-scoring records for the same primary product.

CVE-2016-4010Magento CE and EE before 2.0.6 allows remote attackers to conduct PHP objection injection attacks and execute arbitrary PHP code via…
67This week
CVE-2019-7139An unauthenticated user can execute SQL statements that allow arbitrary read access to the underlying database, which causes sensitive data…
46Plan
CVE-2021-21029Magento Commerce Reflected Cross-site Scripting Vulnerability Could Lead To Arbitrary JavaScript Execution
45Plan

Published before and after this one in the same product

← EarlierCVE-2021-28563Jun 28, 2021 · Magento Commerce improper Authorization via the 'Create Customer' endpoint
26Monitor
← EarlierCVE-2021-28583Jun 28, 2021 · Magento Commerce insecure storage of sensitive documentation
17Monitor
Later →CVE-2021-28585Jun 28, 2021 · Magento Commerce improper input validation in customer customer webapi
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Packagist:magento/community-edition	2.3.7	Package registry (OSV)
Packagist:magento/community-edition	2.4.2-p1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

helpx.adobe.com/security/products/magento/apsb21-30.html

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records