# GHSA-2xpm-cmvw-3jcc: Reflected XSS in Application Logger module

> Reflected XSS in Pimcore's Application Logger allows attackers to steal cookies and hijack user accounts via malicious links.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Mar 2023

## What is GHSA-2xpm-cmvw-3jcc?

GHSA-2xpm-cmvw-3jcc is a cross-site scripting vulnerability in pimcore/pimcore, published on 16 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

### Impact
This vulnerability has the potential to steal a user's cookie and gain unauthorized access to that user's account through the stolen cookie or redirect users to other malicious sites.

### Patches
Update to version 10.5.19 or apply this patch manually https://github.com/pimcore/pimcore/pull/14606.patch

### Workarounds
Apply https://github.com/pimcore/pimcore/pull/14606.patch manually.

### References
https://huntr.dev/bounties/2a64a32d-b1cc-4def-91da-18040d59f356/

## Which versions are affected by GHSA-2xpm-cmvw-3jcc?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | 10.5.19 |
| `pimcore/pimcore` | Packagist | All versions | 10.5.19 |

## How do I fix GHSA-2xpm-cmvw-3jcc?

Upgrade pimcore/pimcore to 10.5.19 or later.

## Is GHSA-2xpm-cmvw-3jcc being exploited?

There is no known exploitation of GHSA-2xpm-cmvw-3jcc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2xpm-cmvw-3jcc and fix it if it is affected.

What it is: GHSA-2xpm-cmvw-3jcc is a cross-site scripting vulnerability in pimcore/pimcore, published on 16 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-2xpm-cmvw-3jcc in the wild and no public exploit code.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; fixed in 10.5.19
- pimcore/pimcore (Packagist): affected all versions; fixed in 10.5.19

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-2xpm-cmvw-3jcc/ (Markdown: https://insights.sbomify.com/GHSA-2xpm-cmvw-3jcc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2xpm-cmvw-3jcc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2xpm-cmvw-3jcc/
Summaries are generated and may contain mistakes; the official description above is the record.