<?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>Kirby REST API — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/kirby-rest-api/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 30 Apr 2026 21:03:20 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/kirby-rest-api/feed.xml" rel="self" type="application/rss+xml"/><item><title>Kirby CMS Missing Authorization Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-kirby-auth-bypass/</link><pubDate>Thu, 30 Apr 2026 21:03:20 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-kirby-auth-bypass/</guid><description>A missing authorization vulnerability in Kirby CMS allows authenticated users to bypass intended access restrictions on pages and files, potentially leading to unauthorized information disclosure and content modification; patched in versions 4.9.0 and 5.4.0.</description><content:encoded><![CDATA[<p>Kirby CMS versions prior to 4.9.0 and between 5.0.0 and 5.3.3 are vulnerable to a missing authorization flaw. This vulnerability impacts Kirby sites where user roles are intentionally configured with restricted access to pages or files through disabled <code>pages.access</code>, <code>pages.list</code>, <code>files.access</code>, or <code>files.list</code> permissions. The issue stems from inconsistent permission checks within the Kirby Panel and REST API, allowing authenticated users to access resources they should not be able to. Updating to versions 4.9.0, 5.4.0, or later resolves this vulnerability by implementing consistent permission checks. The vulnerability is identified as CVE-2026-42137.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An authenticated user logs into the Kirby CMS Panel or REST API.</li>
<li>The user attempts to access a page or file for which their role lacks the necessary <code>pages.access</code>/<code>files.access</code> or <code>pages.list</code>/<code>files.list</code> permissions.</li>
<li>Due to inconsistent permission checks, the user can view the page or file details via the &ldquo;changes&rdquo; dialog in the Panel, even if listing is disabled.</li>
<li>The user accesses the REST API, which, despite direct access checks, fails to properly filter collections or related models (children, drafts, files, etc.).</li>
<li>The attacker views images associated with restricted site, pages, or user resources in lists within the Panel.</li>
<li>The user exploits the incorrect permission check (using <code>pages.access</code> instead of <code>pages.list</code> or <code>files.access</code> instead of <code>files.list</code> in specific API routes).</li>
<li>The user traverses to previous or next files using direct links in the files view, even if those files should not be listable.</li>
<li>The attacker gains unauthorized access to sensitive information or modifies content due to the bypassed permission checks.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>This vulnerability allows authenticated users to bypass intended access restrictions within Kirby CMS, leading to potential unauthorized access to sensitive information and/or unauthorized content modification. The inconsistent permission checks in the Panel and REST API could result in unintended disclosure of data restricted by role-based access controls. Successful exploitation could compromise the confidentiality and integrity of the affected Kirby CMS instance. While the advisory does not list the number of victims, this flaw impacts any Kirby site with restricted roles.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to Kirby CMS version 4.9.0 or 5.4.0 (or later) to patch the vulnerability as recommended in the advisory.</li>
<li>Review user role permissions and blueprint configurations to ensure appropriate access controls are in place after patching, as described in the overview.</li>
<li>Monitor web server logs for unusual API requests to resources that should be restricted, using the rules below, to identify potential exploitation attempts.</li>
<li>Implement rate limiting on API endpoints to mitigate potential brute-force attacks attempting to exploit this or other vulnerabilities.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>authorization</category><category>cms</category><category>web-application</category></item></channel></rss>