Skip to content

GHSA-cj7w-pm77-hvg6 BIT-magento-2022-34253 CVE-2022-34253

Magento XML Injection vulnerability in the Widgets Module

Critical Packagist
Severity
9.1 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
5.01%
Chance of exploitation in the next 30 days. Higher than 92.25% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-91 XML Injection (aka Blind XPath Injection)
Fix
2.3.7-p4
Upgrade magento/community-edition to this version or later

Description

Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (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. Exploitation of this issue does not require user interaction.

Affected versions

Packagist

PackageVulnerableFixed in
magento/community-edition
< 2.3.7-p4
2.3.7-p4
magento/community-edition
>= 2.4.4, < 2.4.5
2.4.5
magento/community-edition
>= 2.4.0, < 2.4.3-p3
2.4.3-p3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

magento/community-edition Packagist → 2.3.7-p4

composer
composer require magento/community-edition:^2.3.7-p4

Severity breakdown

CVSS 3.1 9.1

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

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Weakness

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

The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.

How to prevent it
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-wh92-6q6g-px7j
Magento Community Edition Improper Input Validation vulnerability
Critical Known exploited Also affects magento/community-edition
GHSA-m8cj-3v68-3cxj
Magento Open Source affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerability
Critical Known exploited Also affects magento/community-edition
GHSA-f8fv-f786-9933
Magento improper input validation vulnerability
Critical Known exploited Also affects magento/community-edition
GHSA-qvwr-p3hj-j6jf
Magento vulnerable to privilege escalation due to incorrect authorization
Medium Also affects magento/community-edition
GHSA-pcrx-r49h-x2w5
Magento vulnerable to stored Cross-Site Scripting (XSS)
Medium Also affects magento/community-edition
GHSA-r355-75hw-r8jf
Magento allows incorrect authorization
Medium Also affects magento/community-edition
GHSA-2768-5wmv-cfff
Magento vulnerable to stored Cross-Site Scripting (XSS)
High Also affects magento/community-edition
GHSA-69x9-xp2j-w8g8
Magento provides incorrect authorization through a security feature bypass
High Also affects magento/community-edition
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor