# GHSA-8j7c-682x-r9f2: Magento RCE,XSS and other vulnerabilities

> Attackers can execute arbitrary code or scripts in Magento Commerce and Open Source, potentially compromising the entire e-commerce platform.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-8j7c-682x-r9f2?

GHSA-8j7c-682x-r9f2 is a code injection vulnerability in magento/community-edition, published on 15 May 2024. It can be exploited over the network.

### Official description

Magento Commerce and Open Source 2.3.0, 2.2.7 and 2.1.16 contain multiple security enhancements that help close Remote Code Execution (RCE), Cross-Site Scripting (XSS) and other vulnerabilities.

## Which versions are affected by GHSA-8j7c-682x-r9f2?

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.16 |
| `magento/community-edition` | Packagist | From 2.1 | 2.1.16 |
| `magento/community-edition` | Packagist | From 2.2 | 2.2.7 |
| `magento/community-edition` | Packagist | From 2.2 | 2.2.7 |

## How do I fix GHSA-8j7c-682x-r9f2?

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

## Is GHSA-8j7c-682x-r9f2 being exploited?

There is no known exploitation of GHSA-8j7c-682x-r9f2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8j7c-682x-r9f2 and fix it if it is affected.

What it is: GHSA-8j7c-682x-r9f2 is a code injection vulnerability in magento/community-edition, published on 15 May 2024. It can be exploited over the network.
Exploitation: There is no known exploitation of GHSA-8j7c-682x-r9f2 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.16
- magento/community-edition (Packagist): affected from 2.1; fixed in 2.1.16
- magento/community-edition (Packagist): affected from 2.2; fixed in 2.2.7
- magento/community-edition (Packagist): affected from 2.2; fixed in 2.2.7

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-8j7c-682x-r9f2/ (Markdown: https://insights.sbomify.com/GHSA-8j7c-682x-r9f2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8j7c-682x-r9f2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8j7c-682x-r9f2/
Summaries are generated and may contain mistakes; the official description above is the record.