<?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://cve.radiocsirt.org</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, 15 Oct 2026 10:03:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-316833</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-316833</link>
      <description>EUVD-2026-316833</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-316833</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42137</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42137</link>
      <description>&lt;p&gt;Kirby is an open-source content management system. Prior to versions 4.9.0 and 5.4.0, `pages.access/list` and `files.access/list` permissions are not consistently checked in the Panel and REST API. This issue has been patched in versions 4.9.0 and 5.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kirby is an open-source content management system. Prior to versions 4.9.0 and 5.4.0, `pages.access/list` and `files.access/list` permissions are not consistently checked in the Panel and REST API. This issue has been patched in versions 4.9.0 and 5.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42137</guid>
    </item>
    <item>
      <title>GHSA-85x2-r8xv-ww8c — Kirby CMS's `pages.access/list` and `files.access/list` permissions are not consistently checked in the Panel and REST…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-85x2-r8xv-ww8c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getkirby/cms&lt;/p&gt;
&lt;p&gt;### TL;DR&lt;/p&gt;
&lt;p&gt;This vulnerability affects all Kirby sites where users of a particular role have no permission to access or list pages or files (`pages.access`, `pages.list`, `files.access` or `files.list` permission is disabled). This can be due to configuration in the user blueprint(s), via `options` in the model blueprint(s) or via a combination of both settings.&lt;/p&gt;
&lt;p&gt;**This vulnerability is of high severity for affected sites.**&lt;/p&gt;
&lt;p&gt;Consumers&amp;#39; Kirby sites are *not* affected if they intend all users to be able to access all pages and files of the site. The vulnerability can only be exploited by authenticated users. Write actions are *not* affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;Missing authorization allows authenticated users to perform actions they are not intended to have access to.&lt;/p&gt;
&lt;p&gt;The effects of missing authorization can include unauthorized access to sensitive information as well as unauthorized changes to content or system information.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s user permissions control which user role is allowed to perform specific actions to content models in the CMS. These permissions are defined for each role in the user blueprint (`site/blueprints/users/...`). It is also possible to customize the permissions for each target model in the model blueprints (such as in `site/blueprints/pages/...`) using the `options` feature. The permissions and options together control the authorization of user actions.&lt;/p&gt;
&lt;p&gt;Kirby provides the `pages.access`, `pages.list`, `files.acce…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getkirby/cms&lt;/p&gt;
&lt;p&gt;### TL;DR&lt;/p&gt;
&lt;p&gt;This vulnerability affects all Kirby sites where users of a particular role have no permission to access or list pages or files (`pages.access`, `pages.list`, `files.access` or `files.list` permission is disabled). This can be due to configuration in the user blueprint(s), via `options` in the model blueprint(s) or via a combination of both settings.&lt;/p&gt;
&lt;p&gt;**This vulnerability is of high severity for affected sites.**&lt;/p&gt;
&lt;p&gt;Consumers&amp;#39; Kirby sites are *not* affected if they intend all users to be able to access all pages and files of the site. The vulnerability can only be exploited by authenticated users. Write actions are *not* affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;Missing authorization allows authenticated users to perform actions they are not intended to have access to.&lt;/p&gt;
&lt;p&gt;The effects of missing authorization can include unauthorized access to sensitive information as well as unauthorized changes to content or system information.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s user permissions control which user role is allowed to perform specific actions to content models in the CMS. These permissions are defined for each role in the user blueprint (`site/blueprints/users/...`). It is also possible to customize the permissions for each target model in the model blueprints (such as in `site/blueprints/pages/...`) using the `options` feature. The permissions and options together control the authorization of user actions.&lt;/p&gt;
&lt;p&gt;Kirby provides the `pages.access`, `pages.list`, `files.acce…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-85x2-r8xv-ww8c</guid>
    </item>
  </channel>
</rss>
