CVE-2024-26481 — getkirby/cms
MEDIUMCVE-2024-26481 is a medium-severity (CVSS 4.7) Cross-site Scripting (XSS) vulnerability in getkirby/cms. A fix is available for getkirby/cms — see the affected versions and patch details below.
Kirby vulnerable to self cross-site scripting (self-XSS) in the URL field
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-26481.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-26481 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
getkirby/cms🐘getkirby/cms🐘getkirby/cms🐘getkirby/cms🐘getkirby/cms🐘getkirby/cmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Kirby CMS v4.1.0 was discovered to contain a reflected self-XSS vulnerability via the URL parameter.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | getkirby/cms | all versions | 3.6.6.5composer require getkirby/cms:^3.6.6.5 |
| 🐘Packagist | getkirby/cms | ≥ 3.7.0&&< 3.7.5.4 | 3.7.5.4composer require getkirby/cms:^3.7.5.4 |
| 🐘Packagist | getkirby/cms | ≥ 3.8.0&&< 3.8.4.3 | 3.8.4.3composer require getkirby/cms:^3.8.4.3 |
| 🐘Packagist | getkirby/cms | ≥ 3.9.0&&< 3.9.8.1 | 3.9.8.1composer require getkirby/cms:^3.9.8.1 |
| 🐘Packagist | getkirby/cms | ≥ 3.10.0&&< 3.10.0.1 | 3.10.0.1composer require getkirby/cms:^3.10.0.1 |
| 🐘Packagist | getkirby/cms | ≥ 4.0.0&&< 4.1.1 | 4.1.1composer require getkirby/cms:^4.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update getkirby/cms to 3.6.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-26481 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-26481 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-26481. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-26481 in your dependencies?
O3 Security finds CVE-2024-26481 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.