CVE-2026-45704 is a high-severity incorrect authorization vulnerability in pimcore/pimcore (composer), affecting versions <= 12.3.5. It is fixed in 12.3.6.
Summary CustomReports uses inconsistent authorization between the report listing endpoint and the report detail endpoint. The listing flow filters reports based on report-sharing rules The detail flow only checks generic reports or reportsconfig permissions As a result, a low-privileged backend user who was not granted access to a report can still read that report directly by name even though it does not appear in the user's visible report list. In the local Docker reproduction: The report poc-secret-report was not visible to the low-privileged user in the report list The same user was still able to retrieve the report configuration directly by name Root Cause The listing flow in getReportConfigAction() filters reports through loadForGivenUser(): [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L245) [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L252) CustomReportController.php [Config/Listing/Dao.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Tool/Config/Listing/Dao.php#L44) Config/Listing/Dao.php However, getAction() only checks generic permissions and then loads the report directly by name: [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L146) [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L149) CustomReportController.php CustomReportController.php This means the same report object is protected by different authorization models depending on which endpoint is used. The result is a classic "not visible in list, but readable by direct request" access-control bypass. Impact An attacker can read sensitive report metadata without authorization, including: Report name Grouping information Display and icon metadata Data source configuration Column configuration Sharing settings From the source code, other report endpoints such as data, chart, create-csv, and download-csv also resolve reports by name in a similar way: [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L275) [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L284) CustomReportController.php This report only treats unauthorized report-config retrieval as reproduced. The other execution paths should be verified separately. Preconditions The attacker is an authenticated backend user The attacker has the reports permission The target report is not globally shared and is not shared with that user or the user's roles PoC Reproduction Steps Create a low-privileged user named auditorcustomreports with the reports permission. Create a report named poc-secret-report with: shareGlobally = false sharedUserNames = ['admin'] As auditor_customreports, request the visible report list and verify that poc-secret-report is absent. As the same user, call getAction(name=poc-secret-report) directly. Verify that the response still contains the report configuration. Reproduction command: Reproduction Result Relevant PoC output: This shows that: The current user cannot see the report in the visible report list The same user can still retrieve the report configuration directly This confirms that the share-bypass issue is practically exploitable. Security Impact Unauthorized disclosure of report configuration Disclosure of sharing scope and internal report structure Potential leakage of data-source and query organization details Useful reconnaissance for follow-on unauthorized execution or export paths Remediation Add object-level sharing checks to getAction() equivalent to loadForGivenUser(). Centralize authorization into a single "can current user access this report?" function reused by get, data, chart, create-csv, and download-csv. Return 403 for unshared reports. Add regression tests to ensure that users with reports permission but without report-sharing access cannot retrieve report details.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
composer
pimcore/pimcore (<= 12.3.5)pimcore/pimcore → 12.3.6 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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 instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-45704 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-45704 is reachable in your applications. Get a demo
Upgrade pimcore/pimcore to 12.3.6 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-45704 is a high-severity incorrect authorization vulnerability in pimcore/pimcore (composer), affecting versions <= 12.3.5. It is fixed in 12.3.6. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
pimcore/pimcore (composer) versions <= 12.3.5 is affected.
Yes. CVE-2026-45704 is fixed in 12.3.6. Upgrade to this version or later.
Whether CVE-2026-45704 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
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.
Upgrade pimcore/pimcore to 12.3.6 or later.