Cross-site scripting (XSS) from writer field content in the site frontend
The advisory, in context
Impact
Kirby's writer field stores its formatted content as HTML code. Unlike with other field types, it is not possible to escape HTML special characters against cross-site scripting (XSS) attacks, otherwise the formatting would be lost.
Cross-site scripting (XSS) is a type of vulnerability that allows to execute any kind of JavaScript code inside the site frontend or Panel session of other users. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim.
Because the writer field did not securely sanitize its contents on save, it was possible to inject malicious HTML code into the content file by sending it to Kirby's API directly without using the Panel. This malicious HTML code would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site.
This vulnerability is 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.
You are not affected if you don't use the writer field in any of your blueprints. The attack can only be performed by logged-in users and only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into writer field content.
Patches
We have patched the vulnerability in Kirby 3.5.8 by sanitizing all writer field contents on the backend whenever the content is modified via Kirby's API. Please update to this or a later version to fix the vulnerability.
Credits
Thanks to Azrul Ikhwan Zulkifli (@azrultech) from BAE Systems AI Vulnerability Research Team for responsibly reporting the identified issue.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
From 3.5.0 before 3.5.8
Fixed in 3.5.8
15 explicitly affected versions
3.5.0, 3.5.1, 3.5.1-rc.1, 3.5.2, 3.5.2-rc.1, 3.5.3, 3.5.3.1, 3.5.4, 3.5.5, 3.5.5-rc.1, 3.5.6, 3.5.6-rc.1, 3.5.7, 3.5.7-rc.1, 3.5.7.1
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "3.5.0"
},
{
"fixed": "3.5.8"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.5.0",
"3.5.1",
"3.5.1-rc.1",
"3.5.2",
"3.5.2-rc.1",
"3.5.3",
"3.5.3.1",
"3.5.4",
"3.5.5",
"3.5.5-rc.1",
"3.5.6",
"3.5.6-rc.1",
"3.5.7",
"3.5.7-rc.1",
"3.5.7.1"
]
}