NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

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

mediumCVSS 3.1 4.3GHSA-m3r2-724c-pwgf

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.

Published Jan 15, 2026

Affected packages

pimcore/pimcore

Ecosystem
Composer (PHP)
Affected
>= 12.0.0-RC1, <= 12.3
Fixed in
12.3.1
Check
composer show pimcore/pimcore

pimcore/pimcore

Ecosystem
Composer (PHP)
Affected
<= 11.5.13
Fixed in
11.5.14
Check
composer show pimcore/pimcore

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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"

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

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.

Credited to ytlamal.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Composer (PHP) vulnerabilities

All Composer (PHP) entries