Kirby CMS has cross-site scripting (XSS) in the changes dialog
Published 18 Nov 2025 · Updated 20 Nov 2025
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 package
- Affected
- >=5.0.0 <5.1.4
- Fixed in
- 5.1.4
composer require getkirby/cms:^5.1.4Details
TL;DR
This vulnerability affects all Kirby 5 sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update page titles or usernames.
The attack requires user interaction by another Panel user and *cannot* be automated.
----
Introduction
Cross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the Panel session of the same or other users. In the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.
Such vulnerabilities are critical if you might have potential attackers in your group of authenticated Panel users. They can escalate their privileges if they get access to the Panel session of an admin user. Depending on your site, other JavaScript-powered attacks are possible.
Impact
The "Changes" dialog in the Panel displays all content models (pages, files, users) with changed content, i.e. with content that has not yet been published. Each changed model is listed with its preview image/icon and its title/name.
Attackers could change the title of any page or the name of any user to a malicious string. Then they could modify any content field of the same model without saving, making the model a candidate for display in the "Changes" dialog. If another authenticated user subsequently opened the dialog in their Panel, the malicious code would be executed.
Patches
The problem has been patched in Kirby 5.1.4. Please update to this or a later version to fix the vulnerability.
In the patch release, we have added the required escaping code to signal to the browser the intent of displaying plain text instead of code in the places where the model titles are rendered.
Is GHSA-84hf-8gh5-575j 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.