Pimcore Vulnerable to SQL Injection in getRelationFilterCondition

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U · score source

EPSS

• CVE-2025-27617: 0.50% estimated exploitation activity in the next 30 days; percentile 42.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Authenticated users can craft a filter string used to cause a SQL injection. Details Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer. This code does not look to sanitize inputs: https://github.com/pimcore/pimcore/blob/c721a42c23efffd4ca916511ddb969598d302396/models/DataObject/ClassDefinition/Data/Extension/RelationFilterConditionParser.php#L29-L47 c.f. with https://github.com/pimcore/pimcore/blob/c721a42c23efffd4ca916511ddb969598d302396/models/DataObject/ClassDefinition/Data/Multiselect.php#L332-L347 PoC Complete instructions, including specific configuration details, to reproduce the vulnerability. Impact What kind of vulnerability is it? Who is impacted?

Published by the source

11 Mar 2025, 21:33 UTC

Last modified by the source

11 Mar 2025, 21:33 UTC

Source last checked

26 Oct 2026, 14:29 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qjpx-5m2p-5pgh

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

# Patch Next advisory brief: CVE-2025-27617

Advisory: Pimcore Vulnerable to SQL Injection in getRelationFilterCondition
IDs: CVE-2025-27617, GHSA-qjpx-5m2p-5pgh
Record: https://patchnext.com/advisories/cve-2025-27617 (revision 1, source checked 26 Oct 2026, 14:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pimcore/pimcore 11.5.4. A vendor fix does not mean a deployment is fixed.

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

## 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-qjpx-5m2p-5pgh (GitHub-reviewed advisory GHSA-qjpx-5m2p-5pgh lists affected ranges: Packagist pimcore/pimcore >=0 <11.5.4)

Commands are suggestions: review each one before running it.