CVE-2026-23492: Pimcore has a Blind SQL Injection in Admin Search Find API due to an incomplete fix for CVE-2023-30848

Published Jan 14, 2026
·
Updated

Summary An incomplete SQL injection patch in the Admin Search Find API allows an authenticated attacker to perform blind SQL injection. Although CVE-2023-30848 attempted to mitigate SQL injection by removing SQL comments (--) and catching syntax errors, the fix is insufficient. Attackers can still inject SQL payloads that do not rely on comments and infer database information via blind techniques. This vulnerability affects the admin interface and can lead to database information disclosure.

Details The vulnerability exists in the Admin Search Find API endpoint: /admin/search/search/find In CVE-2023-30848, the following patch was applied:

- SQL comments are removed by replacing -- - SQL syntax errors are caught and replaced with a generic exception

Relevant commit: https://github.com/pimcore/pimcore/commit/25ad8674886f2b938243cbe13e33e204a2e35cc3

Key changes include: // remove sql comments $fields = strreplace('--', '', $fields);

try { $hits = $searcherList->load(); } catch (SyntaxErrorException $syntaxErrorException) { throw new \InvalidArgumentException('Check your arguments.'); } However, this mitigation is incomplete for the following reasons:

1. Only -- is filtered

SQL injection does not require SQL comments. Payloads using boolean conditions, SQL functions, or time-based expressions remain effective.

2. Exception handling only suppresses error output

While syntax errors no longer produce detailed error messages, the underlying SQL query is still executed. This allows attackers to perform blind SQL injection.

3. User-controlled input is still used in SQL query construction The fields[] parameter is attacker-controlled and can be abused to inject SQL expressions into the generated query.

As a result, attackers can craft payloads that do not trigger syntax errors and still influence SQL execution. PoC The following request demonstrates a blind SQL injection via the fields[] parameter.

Boolean-based Blind Injection GET /admin/search/search/find?query=2& fields[]=field1 AND (SELECT CASE WHEN (1=1) THEN 1 ELSE 0 END)=1~field2& filter=[{"property":"value"}]& class=classname Time-based Blind Injection GET /admin/search/search/find?query=2& fields[]=field1 AND IF(1=1,SLEEP(5),0)~field2& filter=[{"property":"value"}]& class=classname Observed behavior:

- When the condition is true, the response is delayed (e.g., ~5 seconds)

- When the condition is false, the response is returned immediately

This confirms that injected SQL expressions are executed successfully. Impact This is a Blind SQL Injection vulnerability.

- Affected users: Systems exposing the Admin Search Find API to authenticated users

- Attack requirements: Authenticated access to the admin interface

- Potential impact:

- Database schema enumeration - Extraction of sensitive data via blind SQL injection - Potential full database compromise depending on database privileges

This issue demonstrates that the fix for CVE-2023-30848 is incomplete.

Other sources

Pimcore is an Open Source Data & Experience Management Platform. Prior to 12.3.1 and 11.5.14, an incomplete SQL injection patch in the Admin Search Find API allows an authenticated attacker to perform blind SQL injection. Although CVE-2023-30848 attempted to mitigate SQL injection by removing SQL comments (--) and catching syntax errors, the fix is insufficient. Attackers can still inject SQL payloads that do not rely on comments and infer database information via blind techniques. This vulnerability affects the admin interface and can lead to database information disclosure. This vulnerability is fixed in 12.3.1 and 11.5.14.

— MITRE

Affected Software

5 affected componentsFixes available
Pimcore pimcore<12.3.1, <11.5.14
composer/pimcore/pimcore<=11.5.13
11.5.14
composer/pimcore/pimcore>=12.0.0-RC1<12.3.1
12.3.1
Pimcore pimcore<11.5.14
Pimcore pimcore>=12.0.0<12.3.1

Event History

Jan 14, 2026
CVE Published
via MITRE·06:21 PM
Data Sourced
via MITRE·06:21 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·09:15 PM
Data Sourced
via GitHub·09:15 PM
DescriptionSeverityWeaknessAffected Software
Feb 19, 58052
Event
via FIRST·12:45 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-23492?

CVE-2026-23492 is classified with a critical severity level due to its potential for exploitation via Blind SQL Injection.

2

How do I fix CVE-2026-23492?

To mitigate CVE-2026-23492, upgrade to Pimcore version 12.3.1 or 11.5.14 or later.

3

What causes CVE-2026-23492?

CVE-2026-23492 is caused by an incomplete SQL injection patch in the Admin Search Find API.

4

Who is affected by CVE-2026-23492?

CVE-2026-23492 affects users of Pimcore versions prior to 12.3.1 and 11.5.14.

5

What potential impact does CVE-2026-23492 have?

The impact of CVE-2026-23492 includes the risk of authenticated attackers performing unauthorized database queries.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203