GitHub Advisoryadvisory · Packagist
GHSA-hqrp-m84v-2m2f Pimcore's Admin Classic Bundle is Missing Function Level Authorization on "Predefined Properties" Listing
MEDIUM
Official page ↗
- Aliases
- CVE-2026-23495
- Ecosystem
- Packagist
- Packages
- pimcore/admin-ui-classic-bundle
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Weaknesses
- CWE-284
- Reviewed
- 2026-01-15
Affected packages
• Packagist pimcore/admin-ui-classic-bundle: >= 2.0.0-RC1, < 2.2.3 → fixed in 2.2.3
• Packagist pimcore/admin-ui-classic-bundle: < 1.7.16 → fixed in 1.7.16
Description
Summary
The API endpoint for listing Predefined Properties in the Pimcore platform lacks adequate server-side authorization checks. Predefined Properties are configurable metadata definitions (e.g., name, key, type, default value) used across documents, assets, and objects to standardize custom attributes and improve editorial workflows, as documented in Pimcore's official properties guide. Testing confirmed that an authenticated backend user without explicit permissions for property management could successfully call the endpoint and retrieve the complete list of these configurations. This exemplifies Broken Access Control (OWASP Top 10 A01:2021), enabling unauthorized access to administrative features and potentially violating role-based access controls inherent to Pimcore's multi-user environment.
Details
The backend user without permission was still able to list "Predefined Properties" item
Step to Reproduce the issue
login as Admin (full permission) and clicked "Predefined Properties"
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 allows low-privileged users to enumerate all Predefined Properties, exposing internal metadata schemas, default values, and configuration details that may reveal business logic, data classification strategies, or sensitive defaults (e.g., proprietary keys or select options). In a PIM system like Pimcore, this could facilitate reconnaissance for further attacks, such as targeted data manipulation or privilege escalation, leading to unauthorized alterations of asset/object properties. For organizations handling regulated content (e.g., e-commerce catalogs under GDPR or PCI DSS), such exposure risks compliance breaches, intellectual property leakage, and operational inconsistencies from unintended property overrides.
Related
Alias · CVE (1)
- CVE-2026-23495 Pimcore's Admin Classic Bundle provides a Backend UI for Pimcore. vulnerability
Weakness · CWE (1)
- CWE-284 Improper Access Control weakness
References
- https://github.com/pimcore/pimcore/security/advisories/GHSA-hqrp-m84v-2m2f web
- https://nvd.nist.gov/vuln/detail/CVE-2026-23495 advisory
- https://github.com/pimcore/admin-ui-classic-bundle/commit/98095949fbeaf11cdf4cadb2989d7454e1b88909 web
- https://github.com/pimcore/admin-ui-classic-bundle/releases/tag/v1.7.16 web
- https://github.com/pimcore/admin-ui-classic-bundle/releases/tag/v2.2.3 web
- https://github.com/pimcore/pimcore package