https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 21:16:19 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-265835 EUVD-2026-265835 https://cve.radiocsirt.org/vuln/euvd-2026-265835 https://cve.radiocsirt.org/vuln/fkie_cve-2026-23494 <p>Pimcore is an Open Source Data &amp; Experience Management Platform. Prior to 12.3.1 and 11.5.14, 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 vulnerability is fixed in 12.3.1 and 11.5.14.</p> <p>Pimcore is an Open Source Data &amp; Experience Management Platform. Prior to 12.3.1 and 11.5.14, 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 vulnerability is fixed in 12.3.1 and 11.5.14.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-23494 https://cve.radiocsirt.org/vuln/ghsa-m3r2-724c-pwgf <p><strong>Affected:</strong> Packagist: pimcore/pimcore</p> <p>### 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.</p> <p>### Details The backend user without permission was still able to list &#34;Static Routes&#34; item</p> <p>### Step to Reproduce the issue login as Admin (full permission) and clicked &#34;Static Routes&#34; &lt;img width=&#34;945&#34; height=&#34;858&#34; alt=&#34;Screenshot 2025-12-10 at 9 36 04 PM&#34; src=&#34;https://github.com/user-attachments/assets/3d4ce400-9bc2-493e-a899-60d5f42ad307&#34; /&gt; Then, captured and saved the request: -List API &lt;img width=&#34;1122&#34; height=&#34;570&#34; alt=&#34;Screenshot 2025-12-10 at 9 44 17 PM&#34; src=&#34;https://github.com/…</p> <p><strong>Affected:</strong> Packagist: pimcore/pimcore</p> <p>### 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.</p> <p>### Details The backend user without permission was still able to list &#34;Static Routes&#34; item</p> <p>### Step to Reproduce the issue login as Admin (full permission) and clicked &#34;Static Routes&#34; &lt;img width=&#34;945&#34; height=&#34;858&#34; alt=&#34;Screenshot 2025-12-10 at 9 36 04 PM&#34; src=&#34;https://github.com/user-attachments/assets/3d4ce400-9bc2-493e-a899-60d5f42ad307&#34; /&gt; Then, captured and saved the request: -List API &lt;img width=&#34;1122&#34; height=&#34;570&#34; alt=&#34;Screenshot 2025-12-10 at 9 44 17 PM&#34; src=&#34;https://github.com/…</p> https://cve.radiocsirt.org/vuln/ghsa-m3r2-724c-pwgf