CVE-2025-30159: Getkirby/kirby Path Traversal Vulnerability

MODERATE
Advisory Identifier: GHSA-fw82-87p8-v6hp
CWE-23 CWE-22
Published
Advisory Summary

CVE-2025-30159 is a MODERATE path traversal vulnerability (CWE-23: Relative Path Traversal) affecting Getkirby/kirby libraries in the Packagist ecosystem. The issue involves kirby vulnerable to path traversal of snippet names in the `snippet()` helper. Remediation is available by upgrading affected packages to version 3.9.8.3, 3.10.1.2, 4.7.1.

CVE-2025-30159 at a Glance

CVE Identifier CVE-2025-30159
GHSA Identifier GHSA-fw82-87p8-v6hp
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-23: Relative Path Traversal
Affected Product Getkirby/kirby
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2025-30159

To remediate this vulnerability, upgrade all affected Getkirby/kirby dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

getkirby/kirby fixed: 3.9.8.3
Upgrade getkirby/kirby to 3.9.8.3
getkirby/kirby fixed: 3.10.1.2
Upgrade getkirby/kirby to 3.10.1.2
getkirby/kirby fixed: 4.7.1
Upgrade getkirby/kirby to 4.7.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for getkirby/kirby

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-30159, inspect your project dependencies for Getkirby/kirby:

inspect dependencies for getkirby/kirby

Analyze the terminal output to locate any version of Getkirby/kirby in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.9.8.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-23: Relative Path Traversal, where the product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. In Getkirby/kirby, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### TL;DR This vulnerability affects all Kirby sites that use the `snippet()` helper or `$kirby->snippet()` method with a dynamic snippet name (such as a snippet name that depends on request or user data). Sites that only use fixed calls to the `snippet()` helper/`$kirby->snippet()` method (i.e. calls with a simple string for the snippet name) are *not* affected. ---- ### Introduction Kirby's `snippet()` helper and `$kirby->snippet()` method (in the following abbreviated to the `snippet()` helper) allow to load PHP snippet files that are normally stored in the `site/snippets` folder or registered by plugins through the `snippets` plugin extension. If the `snippet()` helper is called with an arbitrary snippet name, Kirby first checks if a file with this name exists in the snippets root (which defaults to `site/snippets`). This logic was vulnerable against path traversal attacks. By using special elements such as `..` and `/` separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the `../` sequence, which in most modern operating systems is interpreted as the parent directory of the current location. Because Kirby's `snippet()` helper did not protect against path traversal, the provided snippet name could include special sequences that would cause Kirby to look outside of the configured snippets root and access arbitrary files. ### Impact The missing path traversal check allowed attackers to navigate and access all files on the server that were accessible to the PHP process, including files outside of the snippets root or even outside of the Kirby installation. PHP code within such files was executed. Such attacks first require an attack vector in the site code that is caused by dynamic snippet names, such as `snippet('tags-' . get('tags'))`. It generally also requires knowledge of the site structure and the server's file system by the attacker, although it can be possible to find vulnerable setups through automated methods such as fuzzing. In a vulnerable setup, this could cause damage to the confidentiality and integrity of the server, for example: - it could allow the attacker to build a map of the server's file system for subsequent attacks, - it could allow access to configuration files that may contain sensitive information like security tokens or - it could cause the unintended execution of PHP scripts. ### Patches The problem has been patched in [Kirby 3.9.8.3](https://github.com/getkirby/kirby/releases/tag/3.9.8.3), [Kirby 3.10.1.2](https://github.com/getkirby/kirby/releases/tag/3.10.1.2) and [Kirby 4.7.1](https://github.com/getkirby/kirby/releases/tag/4.7.1). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability. In all of the mentioned releases, we have added a check for the snippet path that ensures that the resulting path is contained within the configured snippets root. Snippet paths that point outside of the snippets root will not be loaded. ### Effects on site code If you deliberately use path traversal in your projects, these uses will break after updating to one of the patched versions. Examples of such uses include: - Aliasing a template by loading another template with `snippet('../templates/other-template')`. Robust alternatives are to use `require __DIR__ . '/other-template.php'` or to override the `$page->template()` method in the page model: ```php class AnotherPage extends Page { public function template(): Template { return $this->kirby()->template('other-template'); } } ``` - Loading a snippet from a shared directory in a multisite setup. A robust alternative is to restructure the project so that all sites share a single snippets root that then branches off into subdirectories for each site. If you prefer to keep the original structure, you can use symbolic links (symlinks) in the file system to include the shared directory in the site-specific snippets roots. ### Credits Thanks to Bruno Meilick (@bnomei) for reporting the identified issue. Thanks to Bruno Meilick and Tobias Möritz (@tobimori) for their input on the effects on site code.

CVE-2025-30159 Affected Getkirby/kirby Versions

3 component(s)
Fixed Versions:
3.9.8.33.10.1.24.7.1
Product / Package Ecosystem Affected Versions Fixed Version
getkirby/kirby
Packagist
< 3.9.8.3
3.9.8.3
getkirby/kirby
Packagist
≥ 3.10.0
< 3.10.1.2
3.10.1.2
getkirby/kirby
Packagist
≥ 4.0.0
< 4.7.1
4.7.1

References

Frequently Asked Questions

What is CVE-2025-30159?
CVE-2025-30159 is a security vulnerability in Getkirby/kirby involving Kirby vulnerable to path traversal of snippet names in the `snippet()` helper under CWE-23: Relative Path Traversal.
Which Getkirby/kirby versions are affected?
Affected versions include releases prior to 3.9.8.3, 3.10.1.2, 4.7.1 across affected packages: getkirby/kirby.
What version fixes CVE-2025-30159?
Upgrading to 3.9.8.3, 3.10.1.2, 4.7.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is getkirby/kirby affected?
Yes, getkirby/kirby is affected in releases prior to 3.9.8.3, 3.10.1.2, 4.7.1. Upgrade your dependency to 3.9.8.3, 3.10.1.2, 4.7.1 or later.
What CWE is associated with CVE-2025-30159?
CVE-2025-30159 is classified under CWE-23: Relative Path Traversal (The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.).
How can I check Packagist dependencies for CVE-2025-30159?
Run the dependency tree command: 'inspect dependencies for getkirby/kirby'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fw82-87p8-v6hp",
  "modified" : "2025-05-13T20:02:24Z",
  "published" : "2025-05-13T20:02:23Z",
  "aliases" : [ "CVE-2025-30159" ],
  "summary" : "Kirby vulnerable to path traversal of snippet names in the `snippet()` helper",
  "details" : "### TL;DR\n\nThis vulnerability affects all Kirby sites that use the `snippet()` helper or `$kirby->snippet()` method with a dynamic snippet name (such as a snippet name that depends on request or user data).\n\nSites that only use fixed calls to the `snippet()` helper/`$kirby->snippet()` method (i.e. calls with a simple string for the snippet name) are *not* affected.\n\n----\n\n### Introduction\n\nKirby's `snippet()` helper and `$kirby->snippet()` method (in the following abbreviated to the `snippet()` helper) allow to load PHP snippet files that are normally stored in the `site/snippets` folder or registered by plugins through the `snippets` plugin extension.\n\nIf the `snippet()` helper is called with an arbitrary snippet name, Kirby first checks if a file with this name exists in the snippets root (which defaults to `site/snippets`).\n\nThis logic was vulnerable against path traversal attacks. By using special elements such as `..` and `/` separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the `../` sequence, which in most modern operating systems is interpreted as the parent directory of the current location.\n\nBecause Kirby's `snippet()` helper did not protect against path traversal, the provided snippet name could include special sequences that would cause Kirby to look outside of the configured snippets root and access arbitrary files.\n\n### Impact\n\nThe missing path traversal check allowed attackers to navigate and access all files on the server that were accessible to the PHP process, including files outside of the snippets root or even outside of the Kirby installation. PHP code within such files was executed.\n\nSuch attacks first require an attack vector in the site code that is caused by dynamic snippet names, such as `snippet('tags-' . get('tags'))`. It generally also requires knowledge of the site structure and the server's file system by the attacker, although it can be possible to find vulnerable setups through automated methods such as fuzzing.\n\nIn a vulnerable setup, this could cause damage to the confidentiality and integrity of the server, for example:\n\n- it could allow the attacker to build a map of the server's file system for subsequent attacks,\n- it could allow access to configuration files that may contain sensitive information like security tokens or\n- it could cause the unintended execution of PHP scripts.\n\n### Patches\n\nThe problem has been patched in [Kirby 3.9.8.3](https://github.com/getkirby/kirby/releases/tag/3.9.8.3), [Kirby 3.10.1.2](https://github.com/getkirby/kirby/releases/tag/3.10.1.2) and [Kirby 4.7.1](https://github.com/getkirby/kirby/releases/tag/4.7.1). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerability.\n\nIn all of the mentioned releases, we have added a check for the snippet path that ensures that the resulting path is contained within the configured snippets root. Snippet paths that point outside of the snippets root will not be loaded.\n\n### Effects on site code\n\nIf you deliberately use path traversal in your projects, these uses will break after updating to one of the patched versions.\n\nExamples of such uses include:\n\n- Aliasing a template by loading another template with `snippet('../templates/other-template')`. Robust alternatives are to use `require __DIR__ . '/other-template.php'` or to override the `$page->template()` method in the page model:\n  ```php\n  class AnotherPage extends Page\n  {\n    public function template(): Template\n    {\n      return $this->kirby()->template('other-template');\n    }\n  }\n  ```\n- Loading a snippet from a shared directory in a multisite setup. A robust alternative is to restructure the project so that all sites share a single snippets root that then branches off into subdirectories for each site. If you prefer to keep the original structure, you can use symbolic links (symlinks) in the file system to include the shared directory in the site-specific snippets roots.\n\n### Credits\n\nThanks to Bruno Meilick (@bnomei) for reporting the identified issue.\nThanks to Bruno Meilick and Tobias Möritz (@tobimori) for their input on the effects on site code.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "getkirby/kirby"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.9.8.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "getkirby/kirby"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.10.0"
      }, {
        "fixed" : "3.10.1.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "getkirby/kirby"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.7.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/security/advisories/GHSA-fw82-87p8-v6hp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-30159"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/commit/90acf7ed6d8d9d0697f938edc0940b4a563ddbe7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/getkirby/kirby"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/releases/tag/3.10.1.2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/releases/tag/3.9.8.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getkirby/kirby/releases/tag/4.7.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-23" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-05-13T20:02:23Z",
    "nvd_published_at" : "2025-05-13T15:15:56Z"
  }
}