Skip to content
Noroxi
CVE-2021-36033· NVD / CVE Program· CNA adobe

Magento Commerce Widgets Module XML Injection 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 XML Injection vulnerability in the Widgets Module. An attacker with admin privileges can trigger a specially crafted script to achieve remote code execution.

HighCVSS 7.2 · v3.1—No exploit Fix available
Published
Sep 1, 2021
Updated
Jun 16, 2026
EPSS
3.1% · 87th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
28 / 40 · 7.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.1%

CNA vs NVD score

NVD
7.2
CNA · adobe
9.1
1.9 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
adobeadobe commerce
adobemagento open source

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • adobe adobe commerce2.3.0 and later · up to 2.3.7 inclusive
  • adobe adobe commerce2.4.0 and later · up to 2.4.2 inclusive
  • adobe adobe commerce2.4.2
  • adobe magento open source2.3.0 and later · up to 2.3.7 inclusive
  • adobe magento open source2.4.0 and later · up to 2.4.2 inclusive
  • adobe magento open source2.4.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

  • Adobe Magento Commerce

    • unspecified and later · up to and including 2.4.2affected
    • unspecified and later · up to and including 2.4.2-p1affected
    • unspecified and later · up to and including 2.3.7affected
    • unspecified and later · up to and including Noneaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistmagento/community-editionfrom 2.4.2-p1 · before 2.4.2-p22.4.2-p2
Packagistmagento/community-editionbefore 2.3.7-p12.3.7-p1
Packagistmagento/community-editionall versions—
Packagistmagento/project-community-editionup to and including 2.0.2—

Same product

adobe: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-36020Magento Commerce XML Injection Vulnerability In The 'City' Field Could Lead To Remote Code Execution
    40Plan
  • CVE-2021-36032Magento Commerce Improper Input Validation Could Lead To Information Exposure and Privilege Escalation
    36Monitor
  • CVE-2021-36044Magento Commerce GraphQL Improper Input Validation Could Lead To Denial Of Service
    31Monitor
  • CVE-2021-36030Magento Commerce Improper Input Validation During Checkout Process Could Lead To Privilege Escalation
    31Monitor
  • CVE-2021-36042Magento Commerce API File Option Upload Extension Improper Input Validation Vulnerability Could Lead To Remote Code Execution
    29Monitor
  • CVE-2021-36041Magento Commerce Improper Input Validation Could Lead To Remote Code Execution
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:magento/community-edition2.3.7-p1Package registry (OSV)
Packagist:magento/community-edition2.4.2-p2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-91 · XML Injection (aka Blind XPath Injection)

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records