How severe is GHSA-5pjj-7fq8-9gpf?

No CVSS score has been assigned to GHSA-5pjj-7fq8-9gpf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5pjj-7fq8-9gpf?

GHSA-5pjj-7fq8-9gpf affects the following packages: magento/project-community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-5pjj-7fq8-9gpf?

A fix is available for GHSA-5pjj-7fq8-9gpf; check the affected-versions list above or the advisory for the patched release of magento/project-community-edition, then make sure no transitive dependency still pins the vulnerable range.

How do I detect GHSA-5pjj-7fq8-9gpf in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/project-community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5pjj-7fq8-9gpf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-5pjj-7fq8-9gpf actively exploited in the wild?

No public exploit code has been indexed for GHSA-5pjj-7fq8-9gpf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5pjj-7fq8-9gpf?

GHSA-5pjj-7fq8-9gpf has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5pjj-7fq8-9gpf?

GHSA-5pjj-7fq8-9gpf is classified as CWE-91 (CWE-91). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5pjj-7fq8-9gpf published, and has it been updated?

GHSA-5pjj-7fq8-9gpf was published on May 24, 2022 and was last updated on November 7, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Magento has an XML Injection vulnerability

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

🐘magento/project-community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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 when saving a configurable product. An attacker with admin privileges can trigger a specially crafted script to achieve remote code execution.

Affected Packages

5 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/project-community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	all versions	2.3.7-p1`composer require magento/community-edition:^2.3.7-p1`
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	≥ 2.4.2-p1&&< 2.4.2-p2	2.4.2-p2`composer require magento/community-edition:^2.4.2-p2`
🐘Packagist	`magento/community-edition`	all versions	No fix

Affected Products

2 products · 6 configurations

Application

adobe commerceadobe

≥ 2.4.0 && ≤ 2.4.2

1 version

2.4.2

Application

magento open sourceadobe

≥ 2.4.0 && ≤ 2.4.2

1 version

2.4.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/project-community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-5pjj-7fq8-9gpf; check the affected-versions list above or the advisory for the patched release of magento/project-community-edition, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 when saving a configurable product. An attacker with admin privileges can trigger a specially crafted script to achieve remote code execution.

O3 Security · Impact-Aware SCA

Is GHSA-5pjj-7fq8-9gpf in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Magento has an XML Injection vulnerabilityGHSA-5pjj-7fq8-9gpf