Unrated

Cross Site Scripting (XSS) in Model\DataObject\Data\UrlSlug

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pimcore/pimcore 10.5.17), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Packagist pimcore/pimcore
Affected
< 10.5.17
Fixed in
10.5.17

Sources

GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-76r7-h46w-463r lists affected ranges: Packagist pimcore/pimcore >=0 <10.5.17
VerifiedObserved 26 Oct 2026, 14:05 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation

Exploitation: No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS: not scored
EPSS: No dated EPSS signal available.

Source description

As published by the source; long descriptions are shortened.

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/

Dates and revisions

Published by the source: 15 Feb 2023, 18:17 UTC
Last modified by the source: 15 Feb 2023, 18:17 UTC
Source last checked: 26 Oct 2026, 14:05 UTC

Revision 1 · created · 26 Oct 2026
Published from ghsa record GHSA-76r7-h46w-463r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-76r7-h46w-463r

Advisory: Cross Site Scripting (XSS) in Model\DataObject\Data\UrlSlug
IDs: GHSA-76r7-h46w-463r
Record: https://patchnext.com/advisories/ghsa-76r7-h46w-463r (revision 1, source checked 26 Oct 2026, 14:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pimcore/pimcore 10.5.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pimcore/pimcore: affected < 10.5.17; fixed in 10.5.17

## Suggested inspection (read-only)
- Packagist pimcore/pimcore: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pimcore/pimcore.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-76r7-h46w-463r (GitHub-reviewed advisory GHSA-76r7-h46w-463r lists affected ranges: Packagist pimcore/pimcore >=0 <10.5.17)

Commands are suggestions: review each one before running it.

Loading voting…