# GHSA-83jv-4prm-34g7: Shopware Remote Code Execution Vulnerability

> An attacker can execute arbitrary code on Shopware installations, potentially compromising the entire e-commerce platform.

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

## What is GHSA-83jv-4prm-34g7?

GHSA-83jv-4prm-34g7 is a code injection vulnerability in shopware/shopware, published on 21 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Under certain circumstances it is possible to execute an authorized foreign code in Shopware version prior to 5.2.25.

## Which versions are affected by GHSA-83jv-4prm-34g7?

2 open source packages ship an affected version, including shopware/shopware.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shopware/shopware` | Packagist | From 4.2.0 | 5.2.25 |
| `shopware/shopware` | Packagist | From 4.2.0 | 5.2.25 |

## How do I fix GHSA-83jv-4prm-34g7?

Upgrade shopware/shopware to 5.2.25 or later.

## Is GHSA-83jv-4prm-34g7 being exploited?

There is no known exploitation of GHSA-83jv-4prm-34g7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-83jv-4prm-34g7 and fix it if it is affected.

What it is: GHSA-83jv-4prm-34g7 is a code injection vulnerability in shopware/shopware, published on 21 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-83jv-4prm-34g7 in the wild and no public exploit code.

Affected packages and fixed versions:
- shopware/shopware (Packagist): affected from 4.2.0; fixed in 5.2.25
- shopware/shopware (Packagist): affected from 4.2.0; fixed in 5.2.25

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-83jv-4prm-34g7/ (Markdown: https://insights.sbomify.com/GHSA-83jv-4prm-34g7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-83jv-4prm-34g7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-83jv-4prm-34g7/
Summaries are generated and may contain mistakes; the official description above is the record.