# CVE-2024-41964: Insufficient permission checks in the language settings in Kirby CMS > Attackers with Panel access can manipulate language definitions due to missing permission checks in Kirby CMS. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Aug 2024 - **Updated:** 29 Aug 2024 - **Also known as:** GHSA-jm9m-rqr3-wfmh ## What is CVE-2024-41964? CVE-2024-41964 is a high-severity missing authorization vulnerability in getkirby kirby, published on 29 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Kirby is a CMS targeting designers and editors. 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 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. There are no known workarounds for this vulnerability. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2024-41964? 12 open source packages ship an affected version, including getkirby/cms. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `getkirby/cms` | Packagist | All versions | 3.6.6.6 | | `getkirby/cms` | Packagist | All versions | 3.6.6.6 | | `getkirby/cms` | Packagist | From 3.10.0 | 3.10.1.1 | | `getkirby/cms` | Packagist | From 3.10.0 | 3.10.1.1 | | `getkirby/cms` | Packagist | From 3.7.0 | 3.7.5.5 | | `getkirby/cms` | Packagist | From 3.7.0 | 3.7.5.5 | | `getkirby/cms` | Packagist | From 3.8.0 | 3.8.4.4 | | `getkirby/cms` | Packagist | From 3.8.0 | 3.8.4.4 | | `getkirby/cms` | Packagist | From 3.9.0 | 3.9.8.2 | | `getkirby/cms` | Packagist | From 3.9.0 | 3.9.8.2 | | `getkirby/cms` | Packagist | From 4.0.0 | 4.3.1 | | `getkirby/cms` | Packagist | From 4.0.0 | 4.3.1 | Products: Getkirby Kirby. ## How do I fix CVE-2024-41964? Upgrade getkirby/cms to a fixed version for your release line: 3.6.6.6, 3.10.1.1, 3.7.5.5 or 3.8.4.4. ## Is CVE-2024-41964 being exploited? There is no known exploitation of CVE-2024-41964 in the wild and no public exploit code. ## Other vulnerabilities in getkirby kirby - [CVE-2024-26483](https://insights.sbomify.com/CVE-2024-26483/): Kirby vulnerable to unrestricted file upload of user avatar images (high 8.8) - [CVE-2026-34587](https://insights.sbomify.com/CVE-2026-34587/): Kirby has Server-Side Template Injection (SSTI) via double template resolution in option rendering (high 7.6) - [CVE-2021-29460](https://insights.sbomify.com/CVE-2021-29460/): Cross-site scripting (XSS) from unsanitized uploaded SVG files (high 7.6) - [CVE-2023-38489](https://insights.sbomify.com/CVE-2023-38489/): Kirby vulnerable to Insufficient Session Expiration after a password change (high 7.3) - [CVE-2021-41252](https://insights.sbomify.com/CVE-2021-41252/): Cross-site scripting (XSS) from writer field content in the site frontend (high 7.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-41964 and fix it if it is affected. What it is: CVE-2024-41964 is a high-severity missing authorization vulnerability in getkirby kirby, published on 29 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-41964 in the wild and no public exploit code. Affected packages and fixed versions: - getkirby/cms (Packagist): affected all versions; fixed in 3.6.6.6 - getkirby/cms (Packagist): affected all versions; fixed in 3.6.6.6 - getkirby/cms (Packagist): affected from 3.10.0; fixed in 3.10.1.1 - getkirby/cms (Packagist): affected from 3.10.0; fixed in 3.10.1.1 - getkirby/cms (Packagist): affected from 3.7.0; fixed in 3.7.5.5 - getkirby/cms (Packagist): affected from 3.7.0; fixed in 3.7.5.5 - getkirby/cms (Packagist): affected from 3.8.0; fixed in 3.8.4.4 - getkirby/cms (Packagist): affected from 3.8.0; fixed in 3.8.4.4 - getkirby/cms (Packagist): affected from 3.9.0; fixed in 3.9.8.2 - getkirby/cms (Packagist): affected from 3.9.0; fixed in 3.9.8.2 - getkirby/cms (Packagist): affected from 4.0.0; fixed in 4.3.1 - getkirby/cms (Packagist): affected from 4.0.0; fixed in 4.3.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-41964/ (Markdown: https://insights.sbomify.com/CVE-2024-41964/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41964 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41964 - OSV: https://osv.dev/vulnerability/CVE-2024-41964 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-41964/ Summaries are generated and may contain mistakes; the official description above is the record.