How severe is GHSA-mcfc-67vm-j568?

No CVSS score has been assigned to GHSA-mcfc-67vm-j568 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mcfc-67vm-j568?

GHSA-mcfc-67vm-j568 affects the following packages: magento/community-edition (Packagist), magento/community-edition (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mcfc-67vm-j568?

Update magento/community-edition to 2.1.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcfc-67vm-j568 is resolved across your whole dependency graph.

How do I detect GHSA-mcfc-67vm-j568 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-mcfc-67vm-j568 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-mcfc-67vm-j568?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mcfc-67vm-j568 can be triaged on real exposure rather than presence alone.

Is GHSA-mcfc-67vm-j568 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mcfc-67vm-j568 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-mcfc-67vm-j568 published, and has it been updated?

GHSA-mcfc-67vm-j568 was published on May 15, 2024 and was last updated on November 29, 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-mcfc-67vm-j568 — magento/community-edition

GHSA-mcfc-67vm-j568 is a security vulnerability in magento/community-edition. A fix is available for magento/community-edition — see the affected versions and patch details below.

Magento Cross-Site Scripting (XSS) vulnerability

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘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 and Open Source 2.2.6 and 2.1.15 contain multiple security enhancements that help close Cross-Site Scripting (XSS) and other vulnerabilities.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 2.1&&< 2.1.15	2.1.15`composer require magento/community-edition:^2.1.15`
🐘Packagist	`magento/community-edition`	≥ 2.2&&< 2.2.6	2.2.6`composer require magento/community-edition:^2.2.6`

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 2.1.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcfc-67vm-j568 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-mcfc-67vm-j568 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mcfc-67vm-j568. 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 and Open Source 2.2.6 and 2.1.15 contain multiple security enhancements that help close Cross-Site Scripting (XSS) and other vulnerabilities.

O3 Security · Impact-Aware SCA

Is GHSA-mcfc-67vm-j568 in your dependencies?

O3 Security finds GHSA-mcfc-67vm-j568 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