# GHSA-76r7-h46w-463r: Cross Site Scripting (XSS) in Model\DataObject\Data\UrlSlug

> An attacker can inject malicious scripts via XSS in Pimcore, potentially compromising user sessions or data.

- **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:** 15 Feb 2023

## What is GHSA-76r7-h46w-463r?

GHSA-76r7-h46w-463r is a cross-site scripting vulnerability in pimcore/pimcore, published on 15 Feb 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
An attacker can use XSS to send a malicious script to an unsuspecting user.

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

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

### References
https://huntr.dev/bounties/75bc7d07-46a7-4ed9-a405-af4fc47fb422/

## Which versions are affected by GHSA-76r7-h46w-463r?

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


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

## How do I fix GHSA-76r7-h46w-463r?

Upgrade pimcore/pimcore to 10.5.17 or later.

## Is GHSA-76r7-h46w-463r being exploited?

There is no known exploitation of GHSA-76r7-h46w-463r in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-76r7-h46w-463r and fix it if it is affected.

What it is: GHSA-76r7-h46w-463r is a cross-site scripting vulnerability in pimcore/pimcore, published on 15 Feb 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-76r7-h46w-463r in the wild and no public exploit code.

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

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-76r7-h46w-463r/ (Markdown: https://insights.sbomify.com/GHSA-76r7-h46w-463r/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-76r7-h46w-463r

---
From sbomify Insights: https://insights.sbomify.com/GHSA-76r7-h46w-463r/
Summaries are generated and may contain mistakes; the official description above is the record.