GHSA-57f2-8p89-66x6
MEDIUMGHSA-57f2-8p89-66x6 is a medium-severity (CVSS 4.2) Cross-site Scripting (XSS) vulnerability in getkirby/cms. O3 Security confirms whether GHSA-57f2-8p89-66x6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Kirby vulnerable to self cross-site scripting (self-XSS) in the URL field
Blast Radius
getkirby/cms🐘getkirby/cms🐘getkirby/cms🐘getkirby/cms🐘getkirby/cms🐘getkirby/cmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | getkirby/cms | all versions | 3.6.6.5 |
| 🐘Packagist | getkirby/cms | ≥ 3.7.0&&< 3.7.5.4 | 3.7.5.4 |
| 🐘Packagist | getkirby/cms | ≥ 3.8.0&&< 3.8.4.3 | 3.8.4.3 |
| 🐘Packagist | getkirby/cms | ≥ 3.9.0&&< 3.9.8.1 | 3.9.8.1 |
| 🐘Packagist | getkirby/cms | ≥ 3.10.0&&< 3.10.0.1 | 3.10.0.1 |
| 🐘Packagist | getkirby/cms | ≥ 4.0.0&&< 4.1.1 | 4.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update getkirby/cms to 3.6.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-57f2-8p89-66x6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-57f2-8p89-66x6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-57f2-8p89-66x6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-57f2-8p89-66x6 in your dependencies?
O3 detects GHSA-57f2-8p89-66x6 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.