CVE-2026-23492

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 = str_replace('--', '', $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.

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-23492 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.3.1, 11.5.14); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-23492? CVE-2026-23492 is a high-severity SQL injection vulnerability in pimcore/pimcore (composer), affecting versions >= 12.0.0-RC1, < 12.3.1. It is fixed in 12.3.1, 11.5.14. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-23492? CVE-2026-23492 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of pimcore/pimcore are affected by CVE-2026-23492? pimcore/pimcore (composer) versions >= 12.0.0-RC1, < 12.3.1 is affected.
4. Is there a fix for CVE-2026-23492? Yes. CVE-2026-23492 is fixed in 12.3.1, 11.5.14. Upgrade to this version or later.
5. Is CVE-2026-23492 exploitable, and should I be worried? Whether CVE-2026-23492 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-23492 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-23492?
   • Upgrade pimcore/pimcore to 12.3.1 or later
   • Upgrade pimcore/pimcore to 11.5.14 or later