MediumGHSA-rf2p-vh74-7vvhCVE-2026-69127

Kirby: System path exposure from error messages in the REST API

Published 1 Sept 2026 · Updated 1 Sept 2026

Is your project on an affected getkirby/cms?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

getkirby/cmsComposer
Affected
<4.9.5
Fixed in
4.9.5
Update to the fixed version for your release line, for example:composer require getkirby/cms:^4.9.5
getkirby/cmsComposer
Affected
>=5.0.0 <5.5.2
Fixed in
5.5.2
Update to the fixed version for your release line, for example:composer require getkirby/cms:^5.5.2

Details

TL;DR

This vulnerability affects all Kirby sites that have not disabled the REST API with the 'api' => false option.

It was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default content.salt or prepare specialized attacks.

----

Introduction

An information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.

Affected components

Kirby's REST API at /api returns JSON data for each request. If an error occurs during processing of the request, a special error handler converts this error to JSON data that API frontends can handle.

The returned data for errors depends on the debugging mode. If the debug option is enabled, the JSON data contains fields for the path and line of the affected file, the internal exception class and the API route that caused the error. This data is omitted from error responses in production (when the debug option is disabled).

Impact

Some internal errors may contain sensitive information in the error message itself. This is often the case with PHP errors.

In affected releases, the REST API error handler did not sanitize error messages for sensitive information.

This exposed system information like the full source path to external API users, including users without authentication. This could be used to guess the default content.salt or prepare specialized attacks.

Patches

The problem has been patched in Kirby 4.9.5 and Kirby 5.5.2. Please update to one of these or a later version to fix the vulnerability.

In all of the mentioned releases, Kirby has hardened the API error handler to only expose full error messages for exceptions in the Kirby\Exception namespace. All other errors are only exposed in debug mode (with disguised paths, keeping only the paths relative to the Kirby installation). Outside of debug mode, general exceptions and PHP errors are replaced with a generic error message.

Credits

Thanks to Peter Levashov (@petersevera) for responsibly reporting the identified issue.

Is GHSA-rf2p-vh74-7vvh in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected getkirby/cms, and gives you the command that fixes it.

More advisories for getkirby/cms

  • MediumCVE-2026-75592Kirby: Access to image files outside of the site root via path traversal in the media handling · 2 Sept 2026
  • HighCVE-2026-71415Kirby: File upload permissions are not checked during processing of chunk data · 31 Aug 2026
  • HighCVE-2026-75594Kirby: Access to image files and limited access to JSON files outside of the site root via path traversal in the media handling · 31 Aug 2026
  • HighCVE-2026-54005Kirby: `pages.access` permission is not checked in the `site/find` REST API route · 18 Jun 2026
  • MediumCVE-2026-54004Kirby: Access to files of top-level drafts is not protected by permissions · 18 Jun 2026
  • CriticalCVE-2026-54003Kirby: External Initialization of the Panel on reverse proxy setups with the `Forwarded` header · 18 Jun 2026
All 51 advisories for getkirby/cms

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.