Quick answers
- Is CVE-2026-42069 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42069 being exploited in the wild.
- How severe is CVE-2026-42069?
- High severity, with a CVSS score of 6.5, published 9 May 2026.
- Which products and versions are affected?
- Kirby <= 4.8.0, >= 5.0.0, <= 5.3.3, <= 4.8.0, 5.0.0 to 5.3.3, <= 4.8.0, 5.0.0-5.3.3; getkirby/cms (Packagist) ECOSYSTEM:introduced=0,fixed=4.9.0.
- Is there a fix for CVE-2026-42069?
- Yes. getkirby/cms (Packagist): upgrade to 4.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42069 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42069?
- Check whether you run Kirby or getkirby/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- getkirby/cms (Packagist): upgrade to 4.9.0 or later
composer require getkirby/cms:^4.9.0
Technical details
A missing authorization vulnerability (CWE-862) exists in Kirby CMS where read access to the site model, user accounts, and role definitions is not governed by the system's permission framework. While write actions were correctly restricted, the 'site.access', 'user.access', and 'user.list' permissions were not implemented or checked in affected versions. An authenticated attacker with Panel access can exploit this to retrieve sensitive information about other users, their roles, and site-wide configurations. The issue is resolved in versions 4.9.0 and 5.4.0 by introducing and enforcing these missing permission checks.
Affected products
- Kirby Kirby CMS <= 4.8.0, 5.0.0 to 5.3.3
Identifiers
- CVE-2026-42069
- GHSA-2h7v-4372-f6x2
Timeline
- 2026-04-23: patched: Versions 4.9.0 and 5.4.0 released
- 2026-04-23: advisory: GitHub Security Advisory published
- 2026-05-09: disclosed: CVE-2026-42069 published to NVD