High

Improper quoting of columns when using setOrderBy() or setGroupBy() on listing classes in Pimcore

  • Disclosed: 22.06.2022
  • Updated: 11.10.2026 10:22

Impact

Pimcore offers developers listing classes to make querying data easier. This listing classes also allow to order or group the results based on one or more columns which should be quoted by default. The actual issue is that quoting is not done properly in both cases, so there's the theoretical possibility to inject custom SQL if the developer is using this methods with input data and not doing proper input validation in advance and so relies on the auto-quoting being done by the listing classes.

Example:

php
// request url: https://example.com/foo?groupBy=o_id`; SELECT SLEEP(20);--

$list = new DataObject\Car\Listing();
$list->setOrderKey($request->get('orderBy'));
$list->setGroupBy($request->get('groupBy'));
$list->load();

Patches

Upgrade to >= 10.4.4 or apply the following patch manually: https://github.com/pimcore/pimcore/commit/21559c6bf0e4e828d33ff7af6e88caecb5ac6549.patch

Workarounds

Apply this patch manually: https://github.com/pimcore/pimcore/commit/21559c6bf0e4e828d33ff7af6e88caecb5ac6549.patch

References

https://github.com/pimcore/pimcore/pull/12444

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package pimcore/pimcore < 10.4.4 10.4.4

References

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

Sources and licenses

OSV / GitHub Advisory Database - GHSA-gvmf-wcx6-p974 - 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. 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. Improper quoting of columns when using setOrderBy() or setGroupBy() on listing classes in Pimcore this entry
    High · 8.1 CVE-2022-31092 < 10.4.4 10.4.4
  24. Critical · 9.8 CVE-2019-18985 < 6.2.2 6.2.2
  25. Critical · 9.8 CVE-2019-18981 < 6.2.2 6.2.2
  26. High · 7.5 CVE-2019-18986 < 6.2.2 6.2.2
  27. High · 8.8 CVE-2019-16317 < 5.7.1 5.7.1
  28. High · 8.8 CVE-2019-16318 < 5.7.1 5.7.1
  29. High CVE-2014-2921 >= 1.4.9, < 2.2.0 2.2.0
  30. High · 8.8 CVE-2018-14057 < 5.3.0 5.3.0
  31. High · 8.8 CVE-2019-10867 < 5.7.1 5.7.1
  32. High · 7.5 CVE-2022-1429 < 10.3.6 10.3.6
  33. High · 7.5 CVE-2022-1339 < 10.3.5 10.3.5
  34. High · 7.5 CVE-2022-1219 < 10.3.5 10.3.5
  35. High · 8.3 CVE-2022-0258 < 10.2.9 10.2.9
  36. High · 7.8 CVE-2022-0263 < 10.2.7 10.2.7
  37. High · 8.0 CVE-2021-39166 < 10.1.2 10.1.2
  38. High · 8.0 CVE-2021-39170 < 10.1.2 10.1.2
  39. High · 8.8 CVE-2021-23405 < 10.0.7 10.0.7
  40. High · 7.2 CVE-2020-7759 >= 6.7.2, < 6.8.3 6.8.3
  41. High · 7.1 CVE-2021-23340 < 6.8.8 6.8.8

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.