# GHSA-mcfc-67vm-j568: Magento Cross-Site Scripting (XSS) vulnerability

> Attackers can inject malicious scripts into Magento pages, potentially stealing user data or hijacking sessions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-mcfc-67vm-j568?

GHSA-mcfc-67vm-j568 is a cross-site scripting vulnerability in magento/community-edition, published on 15 May 2024. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official 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.

## Which versions are affected by GHSA-mcfc-67vm-j568?

4 open source packages ship an affected version, including magento/community-edition.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `magento/community-edition` | Packagist | From 2.1 | 2.1.15 |
| `magento/community-edition` | Packagist | From 2.1 | 2.1.15 |
| `magento/community-edition` | Packagist | From 2.2 | 2.2.6 |
| `magento/community-edition` | Packagist | From 2.2 | 2.2.6 |

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

Upgrade magento/community-edition to a fixed version for your release line: 2.1.15 or 2.2.6.

## Is GHSA-mcfc-67vm-j568 being exploited?

There is no known exploitation of GHSA-mcfc-67vm-j568 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mcfc-67vm-j568 and fix it if it is affected.

What it is: GHSA-mcfc-67vm-j568 is a cross-site scripting vulnerability in magento/community-edition, published on 15 May 2024. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-mcfc-67vm-j568 in the wild and no public exploit code.

Affected packages and fixed versions:
- magento/community-edition (Packagist): affected from 2.1; fixed in 2.1.15
- magento/community-edition (Packagist): affected from 2.1; fixed in 2.1.15
- magento/community-edition (Packagist): affected from 2.2; fixed in 2.2.6
- magento/community-edition (Packagist): affected from 2.2; fixed in 2.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-mcfc-67vm-j568/ (Markdown: https://insights.sbomify.com/GHSA-mcfc-67vm-j568/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mcfc-67vm-j568

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mcfc-67vm-j568/
Summaries are generated and may contain mistakes; the official description above is the record.