High

Pimcore Has an Incomplete Patch for CVE-2023-30848

  • Disclosed: 14.01.2026
  • Updated: 11.10.2026 10:22

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:

php
// 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.

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package pimcore/pimcore >= 12.0.0-RC1, < 12.3.1, < 11.5.14 12.3.1, 11.5.14

References

CVSS score 8.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-89
Platform
Composer
Package
pimcore/pimcore
Disclosed
14.01.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-qvr7-7g55-69xj - CC BY 4.0

Vulnerability history: pimcore/pimcore

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (135) in the archive
Total entries
135
First → latest
12.2019 09.2026
Without a fix
3
Exploited in attacks
0

Severity breakdown

  • Critical 5
  • High 40
  • Medium 90

Disclosures per year

  1. 2019: 1
  2. 2020: 0
  3. 2021: 11
  4. 2022: 43
  5. 2023: 59
  6. 2024: 3
  7. 2025: 2
  8. 2026: 16
Severity:
  1. High · 8.8 CVE-2026-55416 >= 2026.1.0, < 2026.1.6, >= 12.0.0-RC1, < 12.3.10, < 11.5.19 2026.1.6, 12.3.10, 11.5.19
  2. Critical · 9.9 CVE-2026-55634 < 12.3.10, >= 2026.1.0, < 2026.1.6 12.3.10, 2026.1.6
  3. High · 8.5 CVE-2026-55072 >= 2026.1.0, < 2026.1.5, < 12.3.9 2026.1.5, 12.3.9
  4. High · 7.2 CVE-2026-11407 >= 12.0.0-RC1, <= 12.3.8, <= 11.5.14.1 no fix
  5. High CVE-2026-5394 >= 12.0.0-RC1, < 12.3.7, < 11.5.17, >= 2026.1.0, < 2026.1.3 12.3.7, 11.5.17, 2026.1.3
  6. High CVE-2026-45704 >= 12.0.0-RC1, < 12.3.6, < 11.5.17, >= 2026.1.0, < 2026.1.2 12.3.6, 11.5.17, 2026.1.2
  7. High · 8.1 CVE-2026-45260 >= 12.0.0-RC1, < 12.3.7, >= 2026.1.0, < 2026.1.3, < 11.5.17 12.3.7, 2026.1.3, 11.5.17
  8. High · 8.0 CVE-2026-45162 >= 12.0.0-RC1, < 12.3.7, < 11.5.17, >= 2026.1.0, < 2026.1.3 12.3.7, 11.5.17, 2026.1.3
  9. High · 8.7 CVE-2026-44739 >= 2026.1.0, < 2026.1.2, < 11.5.17, >= 12.0.0-RC1, < 12.3.6 2026.1.2, 11.5.17, 12.3.6
  10. High · 8.6 CVE-2026-23493 >= 12.0.0-RC1, < 12.3.1, < 11.5.14 12.3.1, 11.5.14
  11. Pimcore Has an Incomplete Patch for CVE-2023-30848 this entry
    High · 8.8 CVE-2026-23492 >= 12.0.0-RC1, < 12.3.1, < 11.5.14 12.3.1, 11.5.14
  12. High · 8.1 CVE-2024-11954 >= 11.4.2, < 11.5.3 11.5.3
  13. High · 8.8 ghsa-hq76-662x-7mw4 >= 10.6.9.0, < 10.6.9.12, >= 11.1.0.0, < 11.1.6.11 10.6.9.12, 11.1.6.11
  14. High · 7.5 CVE-2024-32871 >= 11.0.0, < 11.2.4 11.2.4
  15. High · 7.2 CVE-2023-3820 < 10.6.4 10.6.4
  16. High · 7.2 CVE-2023-3673 < 10.5.24 10.5.24
  17. High · 8.8 CVE-2023-2338 < 10.5.21 10.5.21
  18. High · 8.8 CVE-2023-30850 < 10.5.21 10.5.21
  19. High · 8.8 CVE-2023-30849 < 10.5.21 10.5.21
  20. High · 8.8 CVE-2023-30848 < 10.5.21 10.5.21
  21. High · 8.8 CVE-2023-25240 < 10.5.16 10.5.16
  22. Critical · 9.8 CVE-2022-39365 < 10.5.9 10.5.9
  23. Critical · 9.8 CVE-2019-18985 < 6.2.2 6.2.2
  24. Critical · 9.8 CVE-2019-18981 < 6.2.2 6.2.2
  25. High · 7.5 CVE-2019-18986 < 6.2.2 6.2.2
  26. High · 8.8 CVE-2019-16317 < 5.7.1 5.7.1
  27. High · 8.8 CVE-2019-16318 < 5.7.1 5.7.1
  28. High CVE-2014-2921 >= 1.4.9, < 2.2.0 2.2.0
  29. High · 8.8 CVE-2018-14057 < 5.3.0 5.3.0
  30. High · 8.8 CVE-2019-10867 < 5.7.1 5.7.1
  31. High · 7.5 CVE-2022-1429 < 10.3.6 10.3.6
  32. High · 7.5 CVE-2022-1339 < 10.3.5 10.3.5
  33. High · 7.5 CVE-2022-1219 < 10.3.5 10.3.5
  34. High · 8.3 CVE-2022-0258 < 10.2.9 10.2.9
  35. High · 7.8 CVE-2022-0263 < 10.2.7 10.2.7
Show more (5) Showing 40 of 45

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.