# GHSA-rrwm-8wqm-gwgv: Cross-site Scripting (XSS) - stored in Print Documents


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 16 Mar 2023

## What is GHSA-rrwm-8wqm-gwgv?

GHSA-rrwm-8wqm-gwgv is a vulnerability in pimcore/pimcore, published on 16 Mar 2023. 

### Official description

### Impact
Stored xss leads to steal cookies and other information of other users

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

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

### References
https://huntr.dev/bounties/31d97442-3f87-439f-83f0-1c7862ef0c7c/

## Which versions are affected by GHSA-rrwm-8wqm-gwgv?

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-rrwm-8wqm-gwgv?

Upgrade pimcore/pimcore to 10.5.19 or later.

## Is GHSA-rrwm-8wqm-gwgv being exploited?

There is no known exploitation of GHSA-rrwm-8wqm-gwgv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-rrwm-8wqm-gwgv and fix it if it is affected.

What it is: GHSA-rrwm-8wqm-gwgv is a vulnerability in pimcore/pimcore, published on 16 Mar 2023. 
Exploitation: There is no known exploitation of GHSA-rrwm-8wqm-gwgv 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-rrwm-8wqm-gwgv/ (Markdown: https://insights.sbomify.com/GHSA-rrwm-8wqm-gwgv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-rrwm-8wqm-gwgv

---
From sbomify Insights: https://insights.sbomify.com/GHSA-rrwm-8wqm-gwgv/
Summaries are generated and may contain mistakes; the official description above is the record.