dbcve.org
OpenmageApplication

CVE-2021-32758

HIGH · 7.2 CVSS v3.1 Published 2021-08-27
Fix available
A fix is available. Upgrade to 19.4.15 / 20.0.11 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenMage Magento LTS versions prior to 19.4.15 and 20.0.11 contain a vulnerability where layout XML configuration allows authenticated admin users to execute arbitrary commands through block methods. This is a code execution vulnerability requiring admin-level access.

MitigationUpgrade OpenMage Magento LTS to version 19.4.15 or 20.0.11 or later to receive the patch for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenmageApplication
Affected:< 19.4.15>= 20.0.00, < 20.0.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the installed OpenMage version file
    Check the composer.json file in the project root for the 'version' field, or look for a VERSION file in the root directory, or check app/etc/config.php for version information
    Affected if You cannot determine the version from these locations
  2. Verify the exact version number
    Run 'composer show openmage/magento-lts' or check the version entry in your package manager if available
    Affected if The version returned is less than 19.4.15 or is 20.0.0 through 20.0.10
  3. Confirm admin access is enabled
    Check if the admin panel is accessible by attempting to reach the admin URL (typically /admin or as configured in app/etc/env.php under 'backend' -> 'frontName')
    Affected if The admin panel is accessible and functional
  4. Identify if non-default layout XML modifications exist
    Review any custom layout XML files in app/design/frontend/ or app/design/adminhtml/ for custom block method declarations that could be exploited
    Affected if Custom layout XML with block method calls exists and the system has admin users

You are affected if your OpenMage version is below 19.4.15 or between 20.0.0 and 20.0.10, your admin interface is accessible, and an attacker could obtain admin credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 19.4.15 / 20.0.11 or later
Fixed in 19.4.1520.0.11
Interim mitigation

Upgrade OpenMage Magento LTS to version 19.4.15 or 20.0.11 or later to receive the patch for this vulnerability.

Recommended fix High confidence

OpenMage 19.4.15+ or 20.0.11+ (depending on your major version branch)

  1. Backup your current OpenMage installation and database before proceeding
  2. Review the OpenMage upgrade documentation at https://github.com/OpenMage/magento-lts/wiki/How-to-upgrade
  3. For OpenMage 19.x versions: Upgrade to version 19.4.15 or later (e.g., 19.4.15, 19.4.16, etc.)
  4. For OpenMage 20.x versions: Upgrade to version 20.0.11 or later (e.g., 20.0.11, 20.0.12, etc.)
  5. Run any necessary database migration scripts included in the upgrade
  6. Clear all caches after upgrade (delete var/cache, var/full_page_cache directories)
  7. Verify the upgrade was successful by checking the admin panel and storefront
  8. Test that layout XML functionality works correctly in the admin area
Caveat Review OpenMage release notes for breaking changes between your current version and the target version; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openmage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32758 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data