{"items":[{"id":"NVI-00005787","kind":"vulnerability","title":"Pimcore has a CustomReports Share Bypass","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jwcc-gv4m-93x6","CVE-2026-45704"],"plain_summary":"GitHub lists this reviewed advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-029802df53085fb14ce32e3c1fec2ba0"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 12.3.6 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2026.1.2 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-22T20:50:36.493Z","value":"7.1 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-78d276671b19697d5d4cd13ede276f87"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.427%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37003. Missing scores are unknown.","source_id":"sr-029802df53085fb14ce32e3c1fec2ba0"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-69c20a91502a847b451765f1d4e62668","url":"https://github.com/advisories/GHSA-jwcc-gv4m-93x6","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jwcc-gv4m-93x6","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:34:12.429Z"},{"id":"sr-9cc47f22b35a9532deb8939bc2c53698","url":"https://github.com/advisories/GHSA-jwcc-gv4m-93x6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jwcc-gv4m-93x6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.970Z"},{"id":"sr-78d276671b19697d5d4cd13ede276f87","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45704","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-45704","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-029802df53085fb14ce32e3c1fec2ba0","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-45704","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.854Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-69c20a91502a847b451765f1d4e62668"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":[">= 12.0.0-RC1, <= 12.3.5"]},{"certainty":"source_listed","source_ids":["sr-69c20a91502a847b451765f1d4e62668"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["<= 11.5.16"]},{"certainty":"source_listed","source_ids":["sr-69c20a91502a847b451765f1d4e62668"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":[">= 2026.1.0, < 2026.1.2"]},{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.6"]},{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]},{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.2"]}],"null_published_at":"2026-11-05T19:10:21.470Z","source_updated_at":"2026-07-10T19:07:35.000Z","source_disclosed_at":"2026-05-27T22:34:01.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.970Z"},{"id":"NVI-00005787","kind":"vulnerability","title":"Pimcore has a CustomReports Share Bypass","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jwcc-gv4m-93x6","CVE-2026-45704"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 12.3.6 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2026.1.2 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-029802df53085fb14ce32e3c1fec2ba0"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-22T20:50:36.493Z","value":"7.1 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-78d276671b19697d5d4cd13ede276f87"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.427%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37003. Missing scores are unknown.","source_id":"sr-029802df53085fb14ce32e3c1fec2ba0"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-9cc47f22b35a9532deb8939bc2c53698","url":"https://github.com/advisories/GHSA-jwcc-gv4m-93x6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jwcc-gv4m-93x6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.970Z"},{"id":"sr-78d276671b19697d5d4cd13ede276f87","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45704","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-45704","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-029802df53085fb14ce32e3c1fec2ba0","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-45704","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.854Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.6"]},{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]},{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.2"]}],"null_published_at":"2026-11-03T17:49:18.517Z","source_updated_at":"2026-07-10T19:15:11.859Z","source_disclosed_at":"2026-05-27T22:34:01.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.970Z"},{"id":"NVI-00005787","kind":"vulnerability","title":"Pimcore has a CustomReports Share Bypass","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jwcc-gv4m-93x6","CVE-2026-45704"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 12.3.6 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2026.1.2 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-9cc47f22b35a9532deb8939bc2c53698","url":"https://github.com/advisories/GHSA-jwcc-gv4m-93x6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jwcc-gv4m-93x6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.970Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.6"]},{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]},{"certainty":"source_listed","source_ids":["sr-9cc47f22b35a9532deb8939bc2c53698"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"### Summary\n\n`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.\n\n- The listing flow filters reports based on report-sharing rules\n- The detail flow only checks generic `reports` or `reports_config` permissions\n\nAs 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.\n\nIn the local Docker reproduction:\n\n- The report `poc-secret-report` was not visible to the low-privileged user in the report list\n- The same user was still able to retrieve the report configuration directly by name\n\n### Root Cause\n\nThe listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:\n\n- [CustomReportController.php](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/Cus","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.2"]}],"null_published_at":"2026-10-31T22:13:05.838Z","source_updated_at":"2026-07-10T19:15:11.859Z","source_disclosed_at":"2026-05-27T22:34:01.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.970Z"}],"next_cursor":null,"snapshot_revision":"42594"}