# CVE-2024-26481: Kirby vulnerable to self cross-site scripting (self-XSS) in the URL field > Reflected self-XSS in Kirby CMS allows attackers to execute scripts in the victim's browser via a crafted URL. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 22 Feb 2024 - **Updated:** 14 Aug 2024 - **Also known as:** GHSA-57f2-8p89-66x6 ## What is CVE-2024-26481? CVE-2024-26481 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Kirby CMS v4.1.0 was discovered to contain a reflected self-XSS vulnerability via the URL parameter. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-26481? 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.5 | | `getkirby/cms` | Packagist | All versions | 3.6.6.5 | | `getkirby/cms` | Packagist | From 3.10.0 | 3.10.0.1 | | `getkirby/cms` | Packagist | From 3.10.0 | 3.10.0.1 | | `getkirby/cms` | Packagist | From 3.7.0 | 3.7.5.4 | | `getkirby/cms` | Packagist | From 3.7.0 | 3.7.5.4 | | `getkirby/cms` | Packagist | From 3.8.0 | 3.8.4.3 | | `getkirby/cms` | Packagist | From 3.8.0 | 3.8.4.3 | | `getkirby/cms` | Packagist | From 3.9.0 | 3.9.8.1 | | `getkirby/cms` | Packagist | From 3.9.0 | 3.9.8.1 | | `getkirby/cms` | Packagist | From 4.0.0 | 4.1.1 | | `getkirby/cms` | Packagist | From 4.0.0 | 4.1.1 | Products: Getkirby Kirby. ## How do I fix CVE-2024-26481? Upgrade getkirby/cms to a fixed version for your release line: 3.6.6.5, 3.10.0.1, 3.7.5.4 or 3.8.4.3. ## Is CVE-2024-26481 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-26481 exists. ## Other vulnerabilities in n/a - [CVE-2024-26483](https://insights.sbomify.com/CVE-2024-26483/): Kirby vulnerable to unrestricted file upload of user avatar images (high 8.8) - [CVE-2024-41964](https://insights.sbomify.com/CVE-2024-41964/): Insufficient permission checks in the language settings in Kirby CMS (high 8.1) - [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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-26481 and fix it if it is affected. What it is: CVE-2024-26481 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-26481 exists. Affected packages and fixed versions: - getkirby/cms (Packagist): affected all versions; fixed in 3.6.6.5 - getkirby/cms (Packagist): affected all versions; fixed in 3.6.6.5 - getkirby/cms (Packagist): affected from 3.10.0; fixed in 3.10.0.1 - getkirby/cms (Packagist): affected from 3.10.0; fixed in 3.10.0.1 - getkirby/cms (Packagist): affected from 3.7.0; fixed in 3.7.5.4 - getkirby/cms (Packagist): affected from 3.7.0; fixed in 3.7.5.4 - getkirby/cms (Packagist): affected from 3.8.0; fixed in 3.8.4.3 - getkirby/cms (Packagist): affected from 3.8.0; fixed in 3.8.4.3 - getkirby/cms (Packagist): affected from 3.9.0; fixed in 3.9.8.1 - getkirby/cms (Packagist): affected from 3.9.0; fixed in 3.9.8.1 - getkirby/cms (Packagist): affected from 4.0.0; fixed in 4.1.1 - getkirby/cms (Packagist): affected from 4.0.0; fixed in 4.1.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-26481/ (Markdown: https://insights.sbomify.com/CVE-2024-26481/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26481 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26481 - OSV: https://osv.dev/vulnerability/CVE-2024-26481 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-26481/ Summaries are generated and may contain mistakes; the official description above is the record.