Kirby CMS's system API endpoint leaks installed version and license data to authenticated users
Published 4 May 2026 · Updated 13 May 2026
Is your project on an affected getkirby/cms?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <4.9.0
- Fixed in
- 4.9.0
composer require getkirby/cms:^4.9.0- Affected
- >=5.0.0 <5.4.0
- Fixed in
- 5.4.0
composer require getkirby/cms:^5.4.0Details
TL;DR
This vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users.
----
Introduction
Missing authorization allows authenticated users to perform actions they are not intended to have access to.
The effects of missing authorization can include unauthorized access to sensitive information as well as unauthorized changes to content or system information.
Impact
Kirby's user permissions control which user role is allowed to perform specific actions in the CMS. These permissions are defined for each role in the user blueprint (site/blueprints/users/...). The permissions control the authorization of user actions (with handling of model-specific authorization omitted here for brevity).
Kirby provides the access.system permission (among others) that controls access to the system area of the Kirby Panel. This area contains internal system information like the installed Kirby, plugin and server versions, security state and Kirby license. If the access.system permission is disabled for a user role, users of that role should not be able to access this internal system information. However it is also possible to access some system information via the /api/system REST API endpoint. In affected releases, the response of this endpoint for authenticated users contained the installed Kirby version and the status, type and code of the installed Kirby license. These values are considered sensitive information and should be protected by the access.system permission.
The installed Kirby version and license data can be used by malicious actors during reconnaissance when planning a separate attack.
Patches
The problem has been patched in Kirby 4.9.0 and Kirby 5.4.0. Please update to one of these or a later version to fix the vulnerability.
In all of the mentioned releases, we have protected the version and license properties of the /api/system endpoint with a check for the existing access.system permission. This ensures that the REST API only outputs information that should be accessible to the user via the Panel.
Credits
Kirby thanks @HuajiHD and @0x-bala for responsibly reporting the identified issue.
Is GHSA-x68m-c7jf-2572 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
- MediumCVE-2026-69127Kirby: System path exposure from error messages in the REST API · 1 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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.