<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 20:57:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-45704</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-45704</link>
      <description>&lt;p&gt;Pimcore is an Open Source Data &amp;amp; Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.6, CustomReports uses inconsistent authorization between the report listing endpoint and the report detail endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php and bundles/CustomReportsBundle/src/Tool/Config/Listing/Dao.php, allowing a low-privileged backend user with the reports permission to directly request an unshared report such as poc-secret-report by name and read report name, grouping information, display and icon metadata, data source configuration, column configuration, and sharing settings even when shareGlobally is false. This issue is fixed in versions 11.5.17 (LTS) and 12.3.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Pimcore is an Open Source Data &amp;amp; Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.6, CustomReports uses inconsistent authorization between the report listing endpoint and the report detail endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php and bundles/CustomReportsBundle/src/Tool/Config/Listing/Dao.php, allowing a low-privileged backend user with the reports permission to directly request an unshared report such as poc-secret-report by name and read report name, grouping information, display and icon metadata, data source configuration, column configuration, and sharing settings even when shareGlobally is false. This issue is fixed in versions 11.5.17 (LTS) and 12.3.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-45704</guid>
    </item>
    <item>
      <title>GHSA-jwcc-gv4m-93x6 — Pimcore has a CustomReports Share Bypass</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-jwcc-gv4m-93x6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/pimcore&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.&lt;/p&gt;
&lt;p&gt;- The listing flow filters reports based on report-sharing rules
- The detail flow only checks generic `reports` or `reports_config` permissions&lt;/p&gt;
&lt;p&gt;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&amp;#39;s visible report list.&lt;/p&gt;
&lt;p&gt;In the local Docker reproduction:&lt;/p&gt;
&lt;p&gt;- 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&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:&lt;/p&gt;
&lt;p&gt;- [[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L245)](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/CustomReportController.php#L252)#L245)
- [[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L253)](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomRepo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/pimcore&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`CustomReports` uses inconsistent authorization between the report listing endpoint and the report detail endpoint.&lt;/p&gt;
&lt;p&gt;- The listing flow filters reports based on report-sharing rules
- The detail flow only checks generic `reports` or `reports_config` permissions&lt;/p&gt;
&lt;p&gt;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&amp;#39;s visible report list.&lt;/p&gt;
&lt;p&gt;In the local Docker reproduction:&lt;/p&gt;
&lt;p&gt;- 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&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The listing flow in `getReportConfigAction()` filters reports through `loadForGivenUser()`:&lt;/p&gt;
&lt;p&gt;- [[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L245)](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/CustomReportController.php#L252)#L245)
- [[CustomReportController.php](https://github.com/pimcore/pimcore/security/advisories/pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php#L253)](pimcore-12.3.3/bundles/CustomReportsBundle/src/Controller/Reports/CustomRepo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-jwcc-gv4m-93x6</guid>
    </item>
  </channel>
</rss>
