<?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, 08 Oct 2026 16:58:42 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-75592</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-75592</link>
      <description>&lt;p&gt;Kirby is an open-source content management system. Prior to 4.9.5 and 5.5.2, depending on the release line, Kirby&amp;#39;s media handler used incomplete filesystem containment checks in src/Filesystem/Dir.php and src/Filesystem/F.php through Kirby\Filesystem\Dir::realpath() and Kirby\Filesystem\F::realpath(). The checks accepted a sibling directory whose path shared the intended root&amp;#39;s string prefix, such as /var/www/site2 next to /var/www/site, because they did not require an exact match or a DIRECTORY_SEPARATOR boundary. A remote attacker could use Kirby\Cms\Media::thumb() to create and access thumbnails from image files in a PHP-readable sibling directory when that directory contained a valid .json thumbnail job file, potentially exposing staging sites, backups, or other internal sites and deleting the job file during processing. This issue is fixed in versions 4.9.5 and 5.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kirby is an open-source content management system. Prior to 4.9.5 and 5.5.2, depending on the release line, Kirby&amp;#39;s media handler used incomplete filesystem containment checks in src/Filesystem/Dir.php and src/Filesystem/F.php through Kirby\Filesystem\Dir::realpath() and Kirby\Filesystem\F::realpath(). The checks accepted a sibling directory whose path shared the intended root&amp;#39;s string prefix, such as /var/www/site2 next to /var/www/site, because they did not require an exact match or a DIRECTORY_SEPARATOR boundary. A remote attacker could use Kirby\Cms\Media::thumb() to create and access thumbnails from image files in a PHP-readable sibling directory when that directory contained a valid .json thumbnail job file, potentially exposing staging sites, backups, or other internal sites and deleting the job file during processing. This issue is fixed in versions 4.9.5 and 5.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-75592</guid>
    </item>
    <item>
      <title>GHSA-6j4c-mgqr-qv76 — Kirby: Access to image files outside of the site root via path traversal in the media handling</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6j4c-mgqr-qv76</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 are deployed in a way that their `index` root on the server is next to a second directory that is read-accessible to PHP and shares the same name prefix (such as the site with the index root `/var/www/site` being next to `/var/www/site2`).&lt;/p&gt;
&lt;p&gt;It was possible to create and access thumbnails from media files within such sibling directories that have a valid thumbnail configuration (JSON job file). This can affect staging sites, site backups or other internal sites.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;A path traversal (also known as directory traversal) vulnerability occurs when untrusted input is used to build a filesystem path without properly confining the result to an intended base directory. By injecting sequences such as `../`, an attacker can escape that directory and reach files elsewhere on the server.&lt;/p&gt;
&lt;p&gt;### Affected components&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s media handler processes requests for files in the `media` directory that have not been generated yet. It parses the provided path and finds the correct file or asset to generate a thumbnail of. Each thumbnail needs to have a prepared job file (a metadata file with file extension `.json`) in order to allow the media handler to generate a thumbnail.&lt;/p&gt;
&lt;p&gt;The media handler uses filesystem containment checks in several places that are supposed to prevent breakout of the `media` and `index` roots of the site.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In affected releases, the containment checks were incomplete and did not cover t…&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 are deployed in a way that their `index` root on the server is next to a second directory that is read-accessible to PHP and shares the same name prefix (such as the site with the index root `/var/www/site` being next to `/var/www/site2`).&lt;/p&gt;
&lt;p&gt;It was possible to create and access thumbnails from media files within such sibling directories that have a valid thumbnail configuration (JSON job file). This can affect staging sites, site backups or other internal sites.&lt;/p&gt;
&lt;p&gt;----&lt;/p&gt;
&lt;p&gt;### Introduction&lt;/p&gt;
&lt;p&gt;A path traversal (also known as directory traversal) vulnerability occurs when untrusted input is used to build a filesystem path without properly confining the result to an intended base directory. By injecting sequences such as `../`, an attacker can escape that directory and reach files elsewhere on the server.&lt;/p&gt;
&lt;p&gt;### Affected components&lt;/p&gt;
&lt;p&gt;Kirby&amp;#39;s media handler processes requests for files in the `media` directory that have not been generated yet. It parses the provided path and finds the correct file or asset to generate a thumbnail of. Each thumbnail needs to have a prepared job file (a metadata file with file extension `.json`) in order to allow the media handler to generate a thumbnail.&lt;/p&gt;
&lt;p&gt;The media handler uses filesystem containment checks in several places that are supposed to prevent breakout of the `media` and `index` roots of the site.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In affected releases, the containment checks were incomplete and did not cover t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6j4c-mgqr-qv76</guid>
    </item>
  </channel>
</rss>
