CVE-2026-40099: Kirby's page creation API bypasses the changeStatus permission check via unfiltered isDraft parameter

CVE-2026-40099 · Severity: medium · CVSS 6.5 · Published 2026-04-24

Kirby is an open-source content management system. Kirby's user permissions control which user role is allowed to perform specific actions to content models in the CMS. These permissions are defined for each role in the user blueprint (`site/blueprints/users/...`). It is also possible to customize the permissions for each target model in the model blueprints (such as in `site/blueprints/pages/...`) using the `options` feature. The permissions and options together control the authorization of user actions. For pages, Kirby provides the `pages.create` and `pages.changeStatus` permissions (among others). Prior to versions 4.9.0 and 5.4.0, Kirby checked these permissions independently and only for the respective action. However the `changeStatus` permission didn't take effect on page creation. New pages are created as drafts by default and need to be published by changing the page status of an existing page draft. This is ensured when the page is created via the Kirby Panel. However the REST API allows to override the `isDraft` flag when creating a new page. This allowed authenticated attackers with the `pages.create` permission to immediately create published pages, bypassing the normal editorial workflow. The problem has been patched in Kirby 4.9.0 and Kirby 5.4.0. Kirby has added a check to the page creation rules that ensures that users without the `pages.changeStatus` permission cannot create published pages, only page drafts.

Technologies: Getkirby Kirby, getkirby/cms (Packagist). Vendors: Getkirby, Packagist.

Quick answers

Is CVE-2026-40099 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-40099 being exploited in the wild.
How severe is CVE-2026-40099?
Medium severity, with a CVSS score of 6.5, published 24 April 2026.
Which products and versions are affected?
getkirby/cms (Packagist) ECOSYSTEM:introduced=0,fixed=4.9.0.
Is there a fix for CVE-2026-40099?
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.
Am I affected by CVE-2026-40099?
Check whether you run Getkirby 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

Affected products

  • Getkirby Kirby
  • getkirby/cms (Packagist) ECOSYSTEM:introduced=0,fixed=4.9.0

Identifiers

  • CVE-2026-40099
  • GHSA-w942-j9r6-hr6r

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.