Magento vulnerable to denial of serviceGHSA-xgfm-992v-h2hr
HIGHGHSA-xgfm-992v-h2hr is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in magento/project-community-edition. A fix is available for magento/project-community-edition — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xgfm-992v-h2hr.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
magento/project-community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition+2 moreReal-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.9-alpha1, 2.4.8-p1, 2.4.7-p6, 2.4.6-p11, 2.4.5-p13, 2.4.4-p14 and earlier are affected by an Improper Input Validation vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability by providing specially crafted input, causing the application to crash or become unresponsive. Exploitation of this issue does not require user interaction.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | magento/project-community-edition | all versions | No fix |
| 🐘Packagist | magento/community-edition | ≥ 2.4.9-alpha1&&< 2.4.9-alpha2 | 2.4.9-alpha2composer require magento/community-edition:^2.4.9-alpha2 |
| 🐘Packagist | magento/community-edition | ≥ 2.4.8-beta1&&< 2.4.8-p2 | 2.4.8-p2composer require magento/community-edition:^2.4.8-p2 |
| 🐘Packagist | magento/community-edition | ≥ 2.4.7-beta1&&< 2.4.7-p7 | 2.4.7-p7composer require magento/community-edition:^2.4.7-p7 |
| 🐘Packagist | magento/community-edition | ≥ 2.4.6-p1&&< 2.4.6-p12 | 2.4.6-p12composer require magento/community-edition:^2.4.6-p12 |
| 🐘Packagist | magento/community-edition | all versions | 2.4.5-p14composer require magento/community-edition:^2.4.5-p14 |
Affected Products
commerceadobecommerce b2badobemagentoadobeDetection & mitigation playbook
Open-source dependencyDetect
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-xgfm-992v-h2hr; 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
Is GHSA-xgfm-992v-h2hr in your dependencies?
Find it across Packagist, including transitive dependencies.