How severe is GHSA-m8cj-3v68-3cxj?

GHSA-m8cj-3v68-3cxj has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-m8cj-3v68-3cxj?

GHSA-m8cj-3v68-3cxj affects the following packages: magento/community-edition (Packagist), magento/community-edition (Packagist), magento/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-m8cj-3v68-3cxj?

No patched version of magento/community-edition has shipped for GHSA-m8cj-3v68-3cxj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-m8cj-3v68-3cxj in my Packagist dependencies?

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

How do I mitigate GHSA-m8cj-3v68-3cxj 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-m8cj-3v68-3cxj actively exploited in the wild?

Yes. There are 17 known exploit references for GHSA-m8cj-3v68-3cxj, including 10 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-m8cj-3v68-3cxj?

GHSA-m8cj-3v68-3cxj has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-m8cj-3v68-3cxj in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-m8cj-3v68-3cxj (Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-07-17. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-08-07. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-m8cj-3v68-3cxj?

GHSA-m8cj-3v68-3cxj is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-m8cj-3v68-3cxj?

A Nuclei detection template exists for GHSA-m8cj-3v68-3cxj, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-m8cj-3v68-3cxj published, and has it been updated?

GHSA-m8cj-3v68-3cxj was published on June 13, 2024 and was last updated on July 17, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

Magento Open Source affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerabilityGHSA-m8cj-3v68-3cxj

CRITICALFix: magento/magento2@30877fc

GHSA-m8cj-3v68-3cxj is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in magento/community-edition. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-07-17) — treat it as actively exploited and patch now. A fix is available for magento/community-edition — see the affected versions and patch details below.

Also known asBIT-magento-2024-34102CVE-2024-34102

Published

Jun 13, 2024

Updated

Jul 17, 2024

Affected

7 pkgs

Patched

3 / 7

Exploits

17 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-07-17. Federal agencies were required to remediate by 2024-08-07.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-m8cj-3v68-3cxj.

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-m8cj-3v68-3cxj by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

7 pkgs affected

🐘magento/community-edition🐘magento/community-edition🐘magento/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

Adobe Commerce versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerability that could result in arbitrary code execution. An attacker could exploit this vulnerability by sending a crafted XML document that references external entities. Exploitation of this issue does not require user interaction.

Affected Packages

7 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	≥ 2.4.6-p1&&< 2.4.6-p6	2.4.6-p6`composer require magento/community-edition:^2.4.6-p6`
🐘Packagist	`magento/community-edition`	≥ 2.4.5-p1&&< 2.4.5-p8	2.4.5-p8`composer require magento/community-edition:^2.4.5-p8`
🐘Packagist	`magento/community-edition`	all versions	2.4.4-p9`composer require magento/community-edition:^2.4.4-p9`
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	all versions	No fix

Affected Products

3 products · 59 configurations

Application

commerceadobe

6 versions

2.4.22.4.32.4.42.4.52.4.62.4.7

Application

commerce webhooksadobe

≥ 1.2.0 && < 1.5.0

range

Application

magentoadobe

4 versions

2.4.42.4.52.4.62.4.7

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.