How severe is GHSA-6wm4-3rjj-c8xx?

No CVSS score has been assigned to GHSA-6wm4-3rjj-c8xx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6wm4-3rjj-c8xx?

GHSA-6wm4-3rjj-c8xx affects the following packages: magento/community-edition (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6wm4-3rjj-c8xx?

Update magento/community-edition to 1.9.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wm4-3rjj-c8xx is resolved across your whole dependency graph.

How do I detect GHSA-6wm4-3rjj-c8xx 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-6wm4-3rjj-c8xx 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-6wm4-3rjj-c8xx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6wm4-3rjj-c8xx can be triaged on real exposure rather than presence alone.

Is GHSA-6wm4-3rjj-c8xx actively exploited in the wild?

No public exploit code has been indexed for GHSA-6wm4-3rjj-c8xx 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.

When was GHSA-6wm4-3rjj-c8xx published, and has it been updated?

GHSA-6wm4-3rjj-c8xx was published on May 15, 2024 and was last updated on May 15, 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

Not in CISA KEV

GHSA-6wm4-3rjj-c8xx — magento/community-edition

GHSA-6wm4-3rjj-c8xx is a remote code execution vulnerability in magento/community-edition. A fix is available for magento/community-edition — see the affected versions and patch details below.

Magento Security enhancements that help close RCE,XSS,CSRF and other vulnerabilities

Published

May 15, 2024

Updated

May 15, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 15, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘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

SUPEE-10975, Magento Commerce 1.14.4.0 and Open Source 1.9.4.0 contain multiple security enhancements that help close remote code execution (RCE), cross-site scripting (XSS), cross-site request forgery (CSRF) and other vulnerabilities.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 1.5.0.0&&< 1.9.4.0	1.9.4.0`composer require magento/community-edition:^1.9.4.0`

Detection & mitigation playbook

Open-source dependency

Detect
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.
Fix
Update magento/community-edition to 1.9.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wm4-3rjj-c8xx is resolved across your whole dependency graph.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6wm4-3rjj-c8xx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6wm4-3rjj-c8xx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6wm4-3rjj-c8xx in your dependencies?

O3 Security finds GHSA-6wm4-3rjj-c8xx across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works