<?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>Sun, 18 Oct 2026 16:50:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-317415</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-317415</link>
      <description>EUVD-2026-317415</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-317415</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42069</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42069</link>
      <description>&lt;p&gt;Kirby is an open-source content management system. Prior to versions 4.9.0 and 5.4.0, read access to site, user and role information is not gated by permissions. 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, read access to site, user and role information is not gated by permissions. 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-42069</guid>
    </item>
    <item>
      <title>GHSA-2h7v-4372-f6x2 — Kirby CMS's read access to site, user and role information is not gated by permissions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2h7v-4372-f6x2</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 that might have potential attackers in the group of authenticated Panel users.&lt;/p&gt;
&lt;p&gt;**This vulnerability is of high severity for affected sites.**&lt;/p&gt;
&lt;p&gt;Sites using Kirby are *not* affected if they intend all users of the site to be able to list and access the site model and all users and roles, including the content stored within these models. Write actions are *not* affected by this vulnerability as they were gated by permissions before.&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;In affected releases, Kirby did not provide permission settings that control the access to the site model as well as to users and user roles. If the site developer disabled all permissions via the wildcard `&amp;#34;*&amp;#34;: false` setting, this only dis…&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 that might have potential attackers in the group of authenticated Panel users.&lt;/p&gt;
&lt;p&gt;**This vulnerability is of high severity for affected sites.**&lt;/p&gt;
&lt;p&gt;Sites using Kirby are *not* affected if they intend all users of the site to be able to list and access the site model and all users and roles, including the content stored within these models. Write actions are *not* affected by this vulnerability as they were gated by permissions before.&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;In affected releases, Kirby did not provide permission settings that control the access to the site model as well as to users and user roles. If the site developer disabled all permissions via the wildcard `&amp;#34;*&amp;#34;: false` setting, this only dis…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2h7v-4372-f6x2</guid>
    </item>
  </channel>
</rss>
