CVE-2026-23494

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"

Then, captured and saved the request:
-List API

Next, login a backend user with no permission

The copy the "Cookie" and "X-Pimcore-Csrf-Token"

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

-List API

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.

CVE-2026-23494 has a CVSS score of 4.3 (Medium). 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-23494? CVE-2026-23494 is a medium-severity security vulnerability in pimcore/pimcore (composer), affecting versions >= 12.0.0-RC1, <= 12.3. It is fixed in 12.3.1, 11.5.14.
2. How severe is CVE-2026-23494? CVE-2026-23494 has a CVSS score of 4.3 (Medium). 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-23494? pimcore/pimcore (composer) versions >= 12.0.0-RC1, <= 12.3 is affected.
4. Is there a fix for CVE-2026-23494? Yes. CVE-2026-23494 is fixed in 12.3.1, 11.5.14. Upgrade to this version or later.
5. Is CVE-2026-23494 exploitable, and should I be worried? Whether CVE-2026-23494 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-23494 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-23494?
   • Upgrade pimcore/pimcore to 12.3.1 or later
   • Upgrade pimcore/pimcore to 11.5.14 or later