First published: Tue Mar 11 2025(Updated: )
### 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?_
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pimcore E-commerce Framework | <11.5.4 | |
composer/pimcore/pimcore | <11.5.4 | 11.5.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2025-27617 is considered to be high due to the potential for SQL injection vulnerabilities, which can lead to data compromise.
To fix CVE-2025-27617, upgrade to Pimcore version 11.5.4 or later where the vulnerability has been addressed.
CVE-2025-27617 affects users of Pimcore versions prior to 11.5.4 who employ certain filter strings.
CVE-2025-27617 allows authenticated users to conduct SQL injection attacks through crafted filter strings.
There are no documented workarounds for CVE-2025-27617; upgrading to the patched version is the recommended approach.