Medium

Pimcore is Vulnerable to Broken Access Control: Missing Function Level Authorization on "Static Routes" Listing

  • Disclosed: 15.01.2026
  • Updated: 11.10.2026 10:22

Summary

The application fails to enforce proper server-side authorization checks on the API endpoint responsible for reading or listing static routes. In Pimcore, static routes are custom URL patterns defined via the backend interface or the var/config/staticroutes.php file, including details like regex-based patterns, controllers, variables, and priorities. These routes are registered automatically through the PimcoreStaticRoutesBundle and integrated into the MVC routing system. Testing revealed that an authenticated backend user lacking explicit permissions was able to invoke the endpoint (e.g., GET /api/static-routes) and retrieve sensitive route configurations. This violates OWASP A01:2021 Broken Access Control, as function-level authorization is absent, allowing unauthorized access to internal routing metadata. Without validation, the endpoint exposes route structures, potentially revealing application architecture, endpoints, or custom logic intended for administrative roles only.

Details

The backend user without permission was still able to list "Static Routes" item

Step to Reproduce the issue

login as Admin (full permission) and clicked "Static Routes" <img width="945" height="858" alt="Screenshot 2025-12-10 at 9 36 04 PM" src="https://github.com/user-attachments/assets/3d4ce400-9bc2-493e-a899-60d5f42ad307" /> Then, captured and saved the request: -List API <img width="1122" height="570" alt="Screenshot 2025-12-10 at 9 44 17 PM" src="https://github.com/user-attachments/assets/81dfb589-fe5d-46ed-b5ee-869a49c08557" />

Next, login a backend user with no permission <img width="1219" height="744" alt="Screenshot 2025-12-10 at 9 06 12 PM" src="https://github.com/user-attachments/assets/1dada4c4-d907-4477-9773-70dea3ef5816" />

The copy the "Cookie" and "X-Pimcore-Csrf-Token" <img width="1902" height="971" alt="Screenshot 2025-12-10 at 9 10 47 PM" src="https://github.com/user-attachments/assets/63221682-fa14-429b-8665-fc9dd8bed890" />

After that, pasted the copied "Cookie" and "X-Pimcore-Csrf-Token" to captured request

-List API

<img width="1132" height="829" alt="Screenshot 2025-12-10 at 9 47 27 PM" src="https://github.com/user-attachments/assets/4edea3d1-f5d9-4758-9a07-e9d484c92864" />

Impact

Exploitation enables low-privileged users to enumerate static routes, gaining reconnaissance into URL patterns, associated controllers, and parameter handling, which could facilitate targeted attacks like path traversal, injection via exposed variables, or discovery of hidden administrative paths. In a Pimcore environment, this might expose site-specific routing for multi-tenant setups, leading to unauthorized data access, workflow manipulation, or escalation to broader system compromise. Business impacts include intellectual property leakage of custom routing logic, regulatory non-compliance (e.g., GDPR for exposed configs), and increased attack surface for chaining with other vulnerabilities.

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 4.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-284
Platform
Composer
Package
pimcore/pimcore
Disclosed
15.01.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-m3r2-724c-pwgf - 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. Pimcore is Vulnerable to Broken Access Control: Missing Function Level Authorization on "Static Routes" Listing this entry
    Medium · 4.3 CVE-2026-23494 >= 12.0.0-RC1, < 12.3.1, < 11.5.14 12.3.1, 11.5.14
  11. High · 8.6 CVE-2026-23493 >= 12.0.0-RC1, < 12.3.1, < 11.5.14 12.3.1, 11.5.14
  12. High · 8.8 CVE-2026-23492 >= 12.0.0-RC1, < 12.3.1, < 11.5.14 12.3.1, 11.5.14
  13. High · 8.1 CVE-2024-11954 >= 11.4.2, < 11.5.3 11.5.3
  14. 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
  15. High · 7.5 CVE-2024-32871 >= 11.0.0, < 11.2.4 11.2.4
  16. High · 7.2 CVE-2023-3820 < 10.6.4 10.6.4
  17. High · 7.2 CVE-2023-3673 < 10.5.24 10.5.24
  18. High · 8.8 CVE-2023-2338 < 10.5.21 10.5.21
  19. High · 8.8 CVE-2023-30850 < 10.5.21 10.5.21
  20. High · 8.8 CVE-2023-30849 < 10.5.21 10.5.21
  21. High · 8.8 CVE-2023-30848 < 10.5.21 10.5.21
  22. High · 8.8 CVE-2023-25240 < 10.5.16 10.5.16
  23. Critical · 9.8 CVE-2022-39365 < 10.5.9 10.5.9
  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.