# CVE-2026-41325: Kirby is vulnerable to authorization bypass during page, file and user creation via blueprint injection

Source: https://junglewise.ai/threats/cve-2026-41325-kirby-is-vulnerable-to-authorization-bypass-during-page-file-and  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-24. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-41325 · Severity: high · CVSS 8.8 · 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. Kirby provides the `pages.create`, `files.create` and `users.create` permissions (among others). These permissions can again be set in the user blueprint and/or in the blueprint of the target model via `options`. Prior to versions 4.9.0 and 5.4.0, Kirby allowed to override the `options` during the creation of pages, files and users by injecting custom dynamic blueprint configuration into the model data. The injected `options` could include `'create' => true`, which then caused an override of the permissions and options configured by the site developer in the user and model blueprints. The problem has been patched in Kirby 4.9.0 and Kirby 5.4.0. The patched versions have updated the normalization code that is used during the creation of pages, files and users to include a filter for the `blueprint` property. This prevents the injection of dynamic blueprint configuration into the creation request.

Technologies: [Getkirby Kirby](https://junglewise.ai/threats/technologies/getkirby-kirby-1), [getkirby/cms (Packagist)](https://junglewise.ai/threats/technologies/getkirby-cms). Vendors: [Getkirby](https://junglewise.ai/threats/vendors/getkirby), [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2026-41325 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-41325 being exploited in the wild.

**How severe is CVE-2026-41325?** High severity, with a CVSS score of 8.8, 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-41325?** 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-41325?** 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

  ```sh
  composer require getkirby/cms:^4.9.0
  ```


## Affected products

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

## Identifiers

- CVE-2026-41325
- GHSA-6gqr-mx34-wh8r

## References

- [https://api.github.com/users/offset](https://api.github.com/users/offset)
- [https://github.com/offset](https://github.com/offset)
- [https://api.github.com/users/offset/gists%7B/gist_id%7D](https://api.github.com/users/offset/gists%7B/gist_id%7D)
- [https://api.github.com/users/offset/repos](https://api.github.com/users/offset/repos)
- [https://avatars.githubusercontent.com/u/114768995?v=4](https://avatars.githubusercontent.com/u/114768995?v=4)
- [https://api.github.com/users/offset/events%7B/privacy%7D](https://api.github.com/users/offset/events%7B/privacy%7D)

## Related threats

- [Getkirby Kirby authorization bypass in Dynamic Option Generation](https://junglewise.ai/threats/cve-2026-108924-a-vulnerability-was-identified-in-getkirby-kirby-up-to-4-9-5-5-5)
- [Kirby path traversal in media handler via encoded slashes](https://junglewise.ai/threats/cve-2026-75594-kirby-path-traversal-in-media-handler-via-encoded-slashes)
- [Kirby path traversal in media handling via sibling directory bypass](https://junglewise.ai/threats/cve-2026-75592-kirby-path-traversal-in-media-handling-via-sibling-directory)
- [Kirby authorization bypass in REST API file uploads](https://junglewise.ai/threats/cve-2026-71415-kirby-authorization-bypass-in-rest-api-file-uploads)
- [Kirby REST API information disclosure via error messages](https://junglewise.ai/threats/cve-2026-69127-kirby-rest-api-information-disclosure-via-error-messages)