How severe is GHSA-qmq6-jpvg-j547?

GHSA-qmq6-jpvg-j547 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qmq6-jpvg-j547?

GHSA-qmq6-jpvg-j547 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-qmq6-jpvg-j547?

No patched version of magento/project-community-edition has shipped for GHSA-qmq6-jpvg-j547 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-qmq6-jpvg-j547 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/project-community-edition. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qmq6-jpvg-j547 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.

How does O3 Security protect against GHSA-qmq6-jpvg-j547?

O3 pinpoints whether GHSA-qmq6-jpvg-j547 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qmq6-jpvg-j547 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qmq6-jpvg-j547 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-qmq6-jpvg-j547?

GHSA-qmq6-jpvg-j547 has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 85th 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-qmq6-jpvg-j547?

GHSA-qmq6-jpvg-j547 is classified as OS Command Injection (CWE-78), CWE-77 (CWE-77). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-qmq6-jpvg-j547 published, and has it been updated?

GHSA-qmq6-jpvg-j547 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.

GHSA-qmq6-jpvg-j547: magento/project-community… Remote Code Exe…

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk85th percentile-5.87%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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 Improper Neutralization of Special Elements Used In A Command via the Data collection endpoint. An attacker with admin privileges can upload a specially crafted file 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
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	≥ 2.4.2-p1&&< 2.4.2-p2	2.4.2-p2
🐘Packagist	`magento/community-edition`	all versions	No fix

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of magento/project-community-edition has shipped for GHSA-qmq6-jpvg-j547 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
How O3 protects you
O3 pinpoints whether GHSA-qmq6-jpvg-j547 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qmq6-jpvg-j547. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 Improper Neutralization of Special Elements Used In A Command via the Data collection endpoint. An attacker with admin privileges can upload a specially crafted file to achieve remote code execution.

O3 Security · Impact-Aware SCA

Is GHSA-qmq6-jpvg-j547 in your dependencies?

O3 detects GHSA-qmq6-jpvg-j547 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-qmq6-jpvg-j547