What is CVE-2021-36033?

CVE-2021-36033 is a critical-severity security vulnerability in magento/project-community-edition (composer), affecting versions <= 2.0.2. It is fixed in 2.3.7-p1, 2.4.2-p2.

Which packages are affected by CVE-2021-36033?

magento/project-community-edition (composer) versions <= 2.0.2; magento/community-edition (composer) versions < 2.3.7-p1.

Is there a fix for CVE-2021-36033?

Yes. CVE-2021-36033 is fixed in 2.3.7-p1, 2.4.2-p2. Upgrade to this version or later.

Is CVE-2021-36033 exploitable, and should I be worried?

Whether CVE-2021-36033 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2021-36033 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2021-36033 in magento/project-community-edition | Intelligent Application Security

Q: Which packages are affected by CVE-2021-36033?

magento/project-community-edition (composer) versions <= 2.0.2; magento/community-edition (composer) versions < 2.3.7-p1.

Q: Is there a fix for CVE-2021-36033?

Yes. CVE-2021-36033 is fixed in 2.3.7-p1, 2.4.2-p2. Upgrade to this version or later.

Q: Is CVE-2021-36033 exploitable, and should I be worried?

Whether CVE-2021-36033 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2021-36033 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2021-36033?

Upgrade: magento/community-edition to 2.3.7-p1 or later, magento/community-edition to 2.4.2-p2 or later.

Summary

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.

Impact

Affected versions

magento/project-community-edition (<= 2.0.2) magento/community-edition (< 2.3.7-p1) magento/community-edition (= 2.3.7) magento/community-edition (>= 2.4.2-p1, < 2.4.2-p2) magento/community-edition (= 2.4.2)

Security releases

magento/community-edition → 2.3.7-p1 (composer) magento/community-edition → 2.4.2-p2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

magento/community-edition to 2.3.7-p1 or later; magento/community-edition to 2.4.2-p2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2021-36033? CVE-2021-36033 is a critical-severity security vulnerability in magento/project-community-edition (composer), affecting versions <= 2.0.2. It is fixed in 2.3.7-p1, 2.4.2-p2.
Which packages are affected by CVE-2021-36033?
- magento/project-community-edition (composer) (versions <= 2.0.2)
- magento/community-edition (composer) (versions < 2.3.7-p1)
Is there a fix for CVE-2021-36033? Yes. CVE-2021-36033 is fixed in 2.3.7-p1, 2.4.2-p2. Upgrade to this version or later.
Is CVE-2021-36033 exploitable, and should I be worried? Whether CVE-2021-36033 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2021-36033 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2021-36033?
- Upgrade magento/community-edition to 2.3.7-p1 or later
- Upgrade magento/community-edition to 2.4.2-p2 or later

Other vulnerabilities in magento/project-community-edition

CVE-IDSeverityPackage summary

CVE-2025-54265Mediummagento/community-edition: Magento allows incorrect authorization CVE-2025-54263Highmagento/community-edition: Magento provides incorrect authorization through a security feature bypass CVE-2025-54267Mediummagento/project-community-edition: Magento vulnerable to privilege escalation due to incorrect authorization CVE-2025-54266Mediummagento/project-community-edition: Magento vulnerable to stored Cross-Site Scripting (XSS)CVE-2025-54264Highmagento/project-community-edition: Magento vulnerable to stored Cross-Site Scripting (XSS)