Cross-site scripting (XSS) from field and configuration text displayed in the Panel
Published 2 Jul 2021 · 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 package
- Affected
- <3.5.7
- Fixed in
- 3.5.7
composer require getkirby/cms:^3.5.7Details
On Saturday, @hdodov reported that the Panel's ListItem component (used in the pages and files section for example) displayed HTML in page titles as it is. This could be used for cross-site scripting (XSS) attacks.
We used his report as an opportunity to find and fix XSS issues related to dynamic site content throughout the Panel codebase.
Impact
Cross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the Panel session of 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.
Visitors without Panel access can only use this attack vector if your site allows changing site data from a frontend form (for example user self-registration or the creation of pages from a contact or other frontend form). If you validate or sanitize the provided form data, you are already protected against such attacks by external visitors.
Patches
Kirby 3.5.7 contains patches for the following issues we found during our investigation:
- Some translated error and info messages contain placeholders to dynamically insert information like page titles or filenames. While the translation strings are allowed to contain HTML formatting, the dynamic data needs to be protected against XSS attacks. Kirby 3.5.7 now escapes the dynamic data.
- Our
Boxcomponent used to display information for the user supports HTML output for specific use-cases. We found out that the dialogs used in thefiles,pagesandusersfields as well as thefieldssection used it to display raw exception or error messages. These messages are now escaped. - The users and settings views display user and language data using the
ListItemcomponent that supports HTML. We now escape the dynamic data before it is passed to theListItemcomponent. - Some of our sections and fields support HTML for their
text,helpand/orinfoproperties. This allows custom formatting from the blueprint, but also caused the original issue reported to us that allowed to inject HTML code from the content itself. Kirby 3.5.7 now escapes the defaulttextdisplayed by thefilesandpagessections (filename/page title), thefiles,pagesandusersfields (filename/page title/username) and by query-basedcheckboxes,radio,tagsandmultiselectfields (default text depending on the used query).
Note: Custom text, help and info queries in blueprints are *not* escaped in 3.5.7. We support HTML in these properties because there are valid use-cases for custom formatting. However there can still be XSS vulnerabilities depending on your use of these properties. In Kirby 3.6 we will provide a new feature that will make it much easier to control whether you want to allow HTML from query placeholders.
Is GHSA-2f2w-349x-vrqm 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.