LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41144: OpenMage LTS authenticated remote code execution through layout update

OpenMage LTS is an e-commerce platform. Prior to versions 19.4.22 and 20.0.19, a layout block was able to bypass the block blacklist to execute remote code. Versions 19.4.22 and 20.0.19 contain a patch for this issue.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-41144 affects OpenMage LTS e-commerce sites. A logged-in attacker could bypass a layout block blacklist and execute remote code on vulnerable versions, potentially compromising store data, integrity, and availability.

Executive priority

Treat this as a high-priority e-commerce platform fix. Prioritize stores handling payments, customer data, or public traffic, because successful exploitation could lead to full server-side compromise.

Technical view

OpenMage magento-lts before 19.4.22 and 20.0.0 through before 20.0.19 is vulnerable to authenticated remote code execution through a layout update blacklist bypass. The CVSS 3.1 score is 8.8 with network access, low complexity, low privileges, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to OpenMage LTS magento-lts deployments in the listed vulnerable version ranges. Internet-facing stores are higher concern because the flaw is network-reachable once an attacker has valid low-privilege authentication or compromises an account.

Exploitation context

The supplied sources do not show CISA KEV listing or confirmed active exploitation. The issue is still serious because it is authenticated RCE with low attack complexity and no user interaction requirement.

Researcher notes

The bundle identifies CWE-77 and a blacklist bypass in layout block handling. Avoid assuming Magento upstream or other forks are affected unless separately confirmed. Evidence provided supports fixed OpenMage releases but not public exploitation status.

Mitigation direction

  • Upgrade OpenMage LTS 19.x deployments to 19.4.22 or later.
  • Upgrade OpenMage LTS 20.x deployments to 20.0.19 or later.
  • Review the GitHub advisory and release notes for vendor-specific guidance.
  • Limit authenticated access to administrative or layout-changing functions.
  • Investigate suspicious authenticated activity on vulnerable stores.

Validation and detection

  • Inventory all OpenMage LTS storefronts and administrative deployments.
  • Compare deployed versions against 19.4.22 and 20.0.19 fixed releases.
  • Confirm the vendor patch or equivalent commit is present.
  • Review accounts with access to layout update functionality.
  • Check logs for unusual authenticated layout or configuration changes.
Prepared
Confidence
high
Sources
6

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-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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-41144 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
5Source 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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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.22, >= 20.0.0, < 20.0.19Listed
Weakness

CWE details

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

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.