| Package | Affected versions | Patched versions |
|---|---|---|
| getkirby/cms | ≥ 3.10.0, < 3.10.1.1≥ 3.7.0, < 3.7.5.5≥ 3.8.0, < 3.8.4.4≥ 3.9.0, < 3.9.8.2≥ 4.0.0, < 4.3.1< 3.6.6.6 | 3.10.1.13.7.5.53.8.4.43.9.8.24.3.13.6.6.6 |
| kirby | ≥ 3.10.0, < 3.10.1.1≥ 3.7.0, < 3.7.5.5≥ 3.8.0, < 3.8.4.4≥ 3.9.0, < 3.9.8.2≥ 4.0.0, < 4.3.1< 3.6.6.6 | 3.10.1.13.7.5.53.8.4.43.9.8.24.3.13.6.6.6 |
This vulnerability affects all Kirby sites with enabled languages option that might have potential attackers in the group of authenticated Panel users.
If you have disabled the languages and/or api option and don't call any methods in your code that cause a write access to languages (language creation, update or deletion), your site is not affected.
Kirby allows to restrict the permissions of specific user roles. Users of that role can only perform permitted actions.
Permissions for creating and deleting languages have already existed and could be configured, but were not enforced by Kirby's frontend or backend code.
A permission for updating existing languages has not existed before the patched versions. So disabling the languages.* wildcard permission for a role could not have prohibited updates to existing language definitions.
The missing permission checks allowed attackers with Panel access to manipulate the language definitions.
The language definitions are at the core of multi-language content in Kirby. Unauthorized modifications with malicious intent can cause significant damage, for example:
languages option was enabled but no language exists, creating the first language will switch Kirby to multi-language mode.Depending on the site code, the result of such actions can cause loss of site availability (e.g. error messages in the site frontend) or integrity (due to changed URLs or removed translations).
The problem has been patched in Kirby 3.6.6.6, Kirby 3.7.5.5, Kirby 3.8.4.4, Kirby 3.9.8.2, Kirby 3.10.1.1, and Kirby 4.3.1. Please update to one of these or a later version to fix the vulnerability.
In all of the mentioned releases, we have added checks for the languages.create and languages.delete permissions that ensure that users without those permissions cannot perform the respective actions. We have also added a new languages.update permission.
Thanks to Sebastian Eberlein of JUNO (@SebastianEberlein-JUNO) for reporting the identified issue.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free