LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36029: Magento Commerce Improper Authorization Vulnerability Could Lead To Remote Code Execution

Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an improper improper authorization vulnerability. An attacker with admin privileges could leverage this vulnerability to achieve remote code execution.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-36029 is a critical Magento Commerce authorization flaw. A user who already has administrator privileges could abuse it to run code on the server, potentially affecting store confidentiality, integrity, and availability. The prompt does not provide evidence of active exploitation.

Executive priority

Treat as urgent for affected Magento Commerce deployments because successful abuse could become server-level compromise. Prioritize patch verification and administrator-account hardening, especially for revenue-critical storefronts.

Technical view

Magento Commerce 2.4.2 and earlier, 2.4.2-p1 and earlier, and 2.3.7 and earlier are affected by CWE-285 improper authorization. CVSS 3.1 is 9.1 with network attack vector, low complexity, high privileges required, no user interaction, changed scope, and high CIA impact.

Likely exposure

Exposure is most likely in organizations still running affected Magento Commerce versions. Practical risk depends heavily on admin-account security because the source states exploitation requires admin privileges.

Exploitation context

CISA KEV is false in the provided data, and no cited source in the bundle confirms active exploitation. The meaningful threat scenario is abuse by a malicious or compromised Magento administrator account.

Researcher notes

The key constraint is PR:H: this is not described as unauthenticated. The bundle does not include exploit details, indicators, or fixed version numbers, so validation should focus on version mapping, Adobe advisory alignment, and admin-control review.

Mitigation direction

  • Inventory all Magento Commerce instances and versions.
  • Review Adobe APSB21-64 for the vendor security update path.
  • Upgrade affected systems according to Adobe guidance.
  • Restrict and review Magento administrator access.
  • Prioritize MFA and least privilege for admin accounts.

Validation and detection

  • Confirm whether any instance matches the affected version ranges.
  • Verify the installed Magento Commerce build against Adobe APSB21-64.
  • Review admin accounts for unnecessary or stale privileges.
  • Check administrative activity logs for suspicious changes.
  • Document patch status for each exposed store.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-285: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-36029 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2021-36029Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobeMagento Commerceunspecified, unspecified, unspecified, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-285 · source CWE mapping

Improper Authorization

Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.