LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21027: Magento Commerce Cross-Site Request Forgery (CSRF) Could Lead To Unauthorized Data Modification

Magento versions 2.4.1 (and earlier), 2.4.0-p1 (and earlier) and 2.3.6 (and earlier) are affected by a cross-site request forgery (CSRF) vulnerability via the GraphQL API. Successful exploitation could lead to unauthorized modification of customer metadata by an unauthenticated attacker. Access to the admin console is not required for successful exploitation.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Magento Commerce flaw could let an unauthenticated attacker trick a user into causing unauthorized customer metadata changes through the GraphQL API. The impact is integrity-focused, not data theft or outage, and the CVSS score is medium.

Executive priority

Treat as a moderate e-commerce integrity risk. Remediate during the normal security patch cycle, faster for internet-facing stores with active customer account workflows.

Technical view

CVE-2021-21027 is a CWE-352 CSRF issue in Magento Commerce 2.4.1 and earlier, 2.4.0-p1 and earlier, and 2.3.6 and earlier. The affected surface is GraphQL API behavior that can permit unauthorized customer metadata modification without admin console access.

Likely exposure

Organizations running affected Magento Commerce versions with reachable GraphQL functionality may be exposed, especially where customer metadata changes are possible through browser-mediated requests.

Exploitation context

The provided sources do not show KEV listing or active exploitation. Exploitation requires user interaction and targets unauthorized data modification, with no admin console access required.

Researcher notes

Evidence supports CSRF via GraphQL with low attack complexity, no privileges, required user interaction, and low integrity impact. The bundle does not provide exploit details, observed exploitation, or fixed version specifics.

Mitigation direction

  • Check Adobe APSB21-08 for the vendor-supported remediation path.
  • Prioritize upgrading affected Magento Commerce versions through official Adobe guidance.
  • Review GraphQL state-changing requests for CSRF protections in supported configurations.
  • Use monitoring to flag unexpected customer metadata changes.

Validation and detection

  • Inventory Magento Commerce versions across production, staging, and backup environments.
  • Confirm whether GraphQL API routes are reachable from untrusted networks.
  • Review logs for unusual customer metadata modifications around exposed storefront activity.
  • Verify remediation status against Adobe APSB21-08, not inferred fixed versions.
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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2021-21027 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
Medium
CVSS
4.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

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
4.3CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.3Medium
CVSS 3.0 vector shape for CVE-2021-21027Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

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-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.