Kirby vulnerable to self cross-site scripting (self-XSS) in the URL field
Published 26 Feb 2024 · Updated 8 Jul 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
- <3.6.6.5
- Fixed in
- 3.6.6.5
composer require getkirby/cms:^3.6.6.5- Affected
- >=3.7.0 <3.7.5.4
- Fixed in
- 3.7.5.4
composer require getkirby/cms:^3.7.5.4- Affected
- >=3.8.0 <3.8.4.3
- Fixed in
- 3.8.4.3
composer require getkirby/cms:^3.8.4.3- Affected
- >=3.9.0 <3.9.8.1
- Fixed in
- 3.9.8.1
composer require getkirby/cms:^3.9.8.1- Affected
- >=3.10.0 <3.10.0.1
- Fixed in
- 3.10.0.1
composer require getkirby/cms:^3.10.0.1- Affected
- >=4.0.0 <4.1.1
- Fixed in
- 4.1.1
composer require getkirby/cms:^4.1.1Details
TL;DR
This vulnerability affects Kirby sites that use the URL field in any blueprint.
A successful attack commonly requires knowledge of the content structure by the attacker as well as social engineering of a user with access to the Panel. The attack *cannot* be automated.
The vulnerability is also limited to self-XSS and *cannot* directly affect other users or visitors of the site.
----
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.
Self cross-site scripting (self-XSS, also called reflected XSS) typically involves a user inadvertently executing malicious code within their own context, often through social engineering techniques. This can occur when a user is tricked into pasting and executing malicious JavaScript code into the browser's developer console, address bar or form fields.
Such vulnerabilities are critical as they allow attackers to gain access to the system or to 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 URL field allows users to open the entered link in a new tab by clicking the link icon inside the field. This can be used to quickly verify whether the entered URL is functional and correct.
In affected versions, Kirby copied the entered URL into the link target of that link button without validating or sanitizing the link. This could be abused by attackers with a javascript: URL that would then be executed in the user's context when the link button was clicked with <kbd>Ctrl+Click</kbd>/<kbd>Cmd+Click</kbd>.
Patches
The problem has been patched in Kirby 3.6.6.5, Kirby 3.7.5.4, Kirby 3.8.4.3, Kirby 3.9.8.1, Kirby 3.10.0.1, and Kirby 4.1.1. Please update to one of these or a later version to fix the vulnerability.
In all of the mentioned releases, we have changed the URL field to only make the link button clickable if the entered URL is valid and safe.
Credits
Thanks to Natwara Archeepsamooth (@PlyNatwara) for responsibly reporting the identified issue.
Is GHSA-57f2-8p89-66x6 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.