LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32758: Layout XML Arbitrary Code Fix

OpenMage Magento LTS is an alternative to the Magento CE official releases. Prior to versions 19.4.15 and 20.0.11, layout XML enabled admin users to execute arbitrary commands via block methods. The latest OpenMage Versions up from v19.4.15 and v20.0.11 have this Issue patched.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenMage Magento LTS had a flaw where a logged-in administrator could use layout XML behavior to run arbitrary commands. This is serious for stores using affected OpenMage versions, but the sources indicate high privileges are required and do not show active exploitation.

Executive priority

Treat this as a high-priority platform maintenance issue for affected OpenMage storefronts. It is not described as actively exploited, but successful abuse could fully compromise confidentiality, integrity, and availability if an admin account is misused.

Technical view

CVE-2021-32758 affects OpenMage magento-lts before 19.4.15 and 20.0.11. The issue is classified as CWE-91 and scored CVSS 3.1 7.2 with network access, low complexity, high privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to OpenMage magento-lts deployments below 19.4.15, or 20.x deployments below 20.0.11. Risk is highest where many administrators, third-party administrators, or potentially compromised admin accounts can modify layout XML or related admin-controlled configuration.

Exploitation context

The source bundle does not identify public exploitation or KEV listing. The vulnerability requires administrator privileges, so practical exploitation depends on malicious insiders, compromised admin accounts, or overly broad admin access.

Researcher notes

Evidence is strongest for affected versions, impact, and fixed releases. The public bundle does not provide exploit status, exploit details, or additional mitigations beyond patched OpenMage versions. No CPE entries were supplied.

Mitigation direction

  • Upgrade OpenMage magento-lts to 19.4.15, 20.0.11, or a later patched version.
  • Review vendor advisory guidance before applying compensating controls.
  • Restrict administrator access to trusted users only.
  • Audit third-party administrator accounts and remove unnecessary privileges.
  • Monitor admin activity until all affected systems are upgraded.

Validation and detection

  • Inventory OpenMage magento-lts versions across all storefronts and environments.
  • Confirm no production instance runs below 19.4.15 or 20.0.11.
  • Review administrator accounts for unnecessary or stale access.
  • Check admin audit logs for unexpected layout or configuration changes.
  • Verify release tags or package metadata after upgrade.
Prepared
Confidence
high
Sources
5

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-91: 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-32758 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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
4Source 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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2021-32758Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenMagemagento-lts< 19.4.15, >= 20, < 20.0.11Listed
Weakness

CWE details

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

CWE-91 · source CWE mapping

XML Injection (aka Blind XPath Injection)

XML Injection (aka Blind XPath Injection) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.