GHSA-rv3r-vqjj-8c76: Getkirby/cms Cross-Site Scripting Vulnerability
HIGHGHSA-rv3r-vqjj-8c76 is a HIGH (CVSS 7.1) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Getkirby/cms libraries in the Packagist ecosystem. The issue involves cross-site scripting from content entered in the tags and multiselect fields. Remediation is available by upgrading affected packages to version 3.5.8.1, 3.6.6.1, 3.7.4.
GHSA-rv3r-vqjj-8c76 at a Glance
Security Impact
CVSS: 7.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N).
How to Fix GHSA-rv3r-vqjj-8c76
To remediate this vulnerability, upgrade all affected Getkirby/cms dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade getkirby/cms to 3.5.8.1
Upgrade getkirby/cms to 3.6.6.1
Upgrade getkirby/cms to 3.7.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for getkirby/cms
How to Check if You Are Affected
To determine whether your application is affected by GHSA-rv3r-vqjj-8c76, inspect your project dependencies for Getkirby/cms:
inspect dependencies for getkirby/cms
Analyze the terminal output to locate any version of Getkirby/cms in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.5.8.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Getkirby/cms, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-rv3r-vqjj-8c76 Affected Getkirby/cms Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
getkirby/cms
|
Packagist |
≥ 3.5.7
< 3.5.8.1
|
3.5.8.1
|
|
getkirby/cms
|
Packagist |
≥ 3.6.0
< 3.6.6.1
|
3.6.6.1
|
|
getkirby/cms
|
Packagist |
≥ 3.7.0
< 3.7.4
|
3.7.4
|
References
Frequently Asked Questions
What is GHSA-rv3r-vqjj-8c76?
Which Getkirby/cms versions are affected?
What version fixes GHSA-rv3r-vqjj-8c76?
Is getkirby/cms affected?
What is the CVSS score of GHSA-rv3r-vqjj-8c76?
What CWE is associated with GHSA-rv3r-vqjj-8c76?
How can I check Packagist dependencies for GHSA-rv3r-vqjj-8c76?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rv3r-vqjj-8c76",
"modified" : "2025-03-24T14:37:40Z",
"published" : "2022-08-30T20:53:03Z",
"aliases" : [ ],
"summary" : "Cross-site scripting from content entered in the tags and multiselect fields",
"details" : "### Introduction\n\nCross-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.\n\nSuch 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.\n\n### Impact\n\nThe tags and multiselect fields allow to select tags from an autocompleted list. The tags field also allows to enter new tags or edit existing tags. Kirby already handled escaping of the autocompleted tags, but unfortunately the Panel used HTML rendering for new or edited tags as well as for custom tags from the content file.\n\nThis allowed **attackers with Panel access** to store malicious HTML code in a tag. The browser of the victim who visited the modified page in the Panel will then have rendered this malicious HTML code.\n\nIt also allowed **self-inflicted XSS attacks** in the tags field (meaning that malicious code is executed in the browser of the user who entered it). This could be used in social engineering attacks where a victim is convinced by an attacker to enter malicious code into a tags field.\n\n**Visitors without Panel access** could *only* use this attack vector if your site allows changing the content of a tags or multiselect field 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.\n\nYou are also *not* affected by these vulnerabilities if your site doesn't have untrustworthy users with Panel access or a way to modify field values from the frontend or if you don't use the tags or multiselect fields.\n\n### Patches\n\nThe problems have been patched in [Kirby 3.5.8.1](https://github.com/getkirby/kirby/releases/tag/3.5.8.1), [Kirby 3.6.6.1](https://github.com/getkirby/kirby/releases/tag/3.6.6.1) and [Kirby 3.7.4](https://github.com/getkirby/kirby/releases/tag/3.7.4). Please update to one of these or a [later version](https://github.com/getkirby/kirby/releases) to fix the vulnerabilities.\n\n**Note:** The fixes for these vulnerabilities have the side effect that values in the tags and multiselect fields that come from dynamic options are displayed with double escaping (e.g. the `&` character is displayed as `&`). In the fix for Kirby 3.5, every value in the tags field is displayed with double escaping when dynamic options are enabled, while dynamic options themselves are displayed with triple escaping. We will fix the double/triple escaping issues with a refactoring of the options fields (tags, multiselect, checkboxes, radio, select and toggles) in Kirby 3.8.\n\n### Workarounds\n\nWe recommend to update to one of the patch releases. If you cannot update immediately, you can work around the issue by disabling the tags and multiselect fields. This can be done by uncommenting these fields from all your blueprints.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "getkirby/cms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.5.7"
}, {
"fixed" : "3.5.8.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "getkirby/cms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.6.0"
}, {
"fixed" : "3.6.6.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "getkirby/cms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.7.0"
}, {
"fixed" : "3.7.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/getkirby/kirby/security/advisories/GHSA-rv3r-vqjj-8c76"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/getkirby/kirby"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-79" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-08-30T20:53:03Z",
"nvd_published_at" : null
}
}