<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Pimcore CustomReports — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/pimcore-customreports/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 27 May 2026 22:35:24 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/pimcore-customreports/feed.xml" rel="self" type="application/rss+xml"/><item><title>Pimcore CustomReports Share Bypass Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-05-pimcore-report-bypass/</link><pubDate>Wed, 27 May 2026 22:35:24 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-pimcore-report-bypass/</guid><description>Pimcore's CustomReports feature has a share bypass vulnerability due to inconsistent authorization checks between the report listing endpoint and the report detail endpoint, allowing low-privileged users to access report configurations without explicit sharing permissions.</description><content:encoded><![CDATA[<p>Pimcore&rsquo;s CustomReports utilizes inconsistent authorization between the report listing endpoint and the report detail endpoint. The report listing flow filters reports based on report-sharing rules, while the detail flow only checks for generic <code>reports</code> or <code>reports_config</code> permissions. As a result, a low-privileged backend user who has been granted the <code>reports</code> permission, but not explicitly granted access to a specific report, can still read that report directly by name, even if the report does not appear in the user&rsquo;s visible report list. The vulnerability resides within the CustomReports bundle and affects Pimcore instances where custom reports with restricted access are in use. This vulnerability allows unauthorized access to sensitive report metadata.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker authenticates as a low-privileged backend user with the <code>reports</code> permission.</li>
<li>The attacker attempts to list available custom reports via the designated endpoint.</li>
<li>The server filters the list of reports based on sharing rules, excluding reports not explicitly shared with the user.</li>
<li>The attacker identifies a target report name through reconnaissance or other means.</li>
<li>The attacker crafts a direct request to the report detail endpoint, specifying the target report name.</li>
<li>The server checks only for generic <code>reports</code> permissions, bypassing the sharing rules enforced in the listing endpoint.</li>
<li>The server retrieves and returns the report configuration to the attacker.</li>
<li>The attacker gains unauthorized access to sensitive report metadata, including report name, data source configuration, and sharing settings.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows unauthorized access to sensitive report metadata, including the report name, grouping information, display and icon metadata, data source configuration, column configuration, and sharing settings. This can lead to information disclosure and potentially further unauthorized actions, depending on the content of the reports. The source code suggests that other report endpoints like <code>data</code>, <code>chart</code>, <code>create-csv</code>, and <code>download-csv</code> might also be vulnerable due to similar resolution-by-name mechanisms.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect Pimcore CustomReports Share Bypass</code> to your SIEM to identify requests to the report detail endpoint (<code>getAction</code>) for reports that are not listed as accessible to the user.</li>
<li>Review and audit all custom report sharing configurations to ensure proper access controls are in place.</li>
<li>Investigate other potentially vulnerable report endpoints, such as <code>data</code>, <code>chart</code>, <code>create-csv</code>, and <code>download-csv</code>, for similar access control bypass issues.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>privilege-escalation</category><category>defense-evasion</category><category>web-application</category></item></channel></rss>