Kirby is vulnerable to authorization bypass during page, file and user creation via blueprint injection
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-863.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| getkirby | kirby | before 4.9.0; 5.0.0 to before 5.4.0 | 4.9.0, 5.4.0 | Patch available | CNA |
| — | getkirby/cms (Packagist) | before 4.9.0 | 4.9.0 | Patch available | GHSA-6gqr-mx34-wh8r |
| — | getkirby/cms (Packagist) | 5.0.0 to before 5.4.0 | 5.4.0 | Patch available | GHSA-6gqr-mx34-wh8r |
- kirby Vendorgetkirby Affected before 4.9.0; 5.0.0 to before 5.4.0 Fixed in 4.9.0, 5.4.0 Patch available CNA
- getkirby/cms (Packagist) Vendor— Affected before 4.9.0 Fixed in 4.9.0 Patch available GHSA-6gqr-mx34-wh8r
- getkirby/cms (Packagist) Vendor— Affected 5.0.0 to before 5.4.0 Fixed in 5.4.0 Patch available GHSA-6gqr-mx34-wh8r
Remediation
- Fix · CNA kirby (getkirby) Fixed in 4.9.0, 5.4.0
- Fix · GHSA-6gqr-mx34-wh8r getkirby/cms (Packagist) Fixed in 4.9.0 Advisory →
- Fix · GHSA-6gqr-mx34-wh8r getkirby/cms (Packagist) Fixed in 5.4.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-41325
- 2026-10-03 Alias added: GHSA-6gqr-mx34-wh8r
References
More getkirby Kirby vulnerabilities
- TI-2024-17440 An arbitrary file upload vulnerability in the Profile Image module of Kirby CMS v4.1.0… CVSS 3.1HIGH 8.8
- TI-2024-17439 An HTML injection vulnerability exists in the Edit Content Layout module of Kirby CMS… CVSS 3.1HIGH 7.1
- TI-2026-23396 Kirby CMS through 5.1.4 allows an authenticated user with 'Editor' permissions to cause a… CVSS 3.1MEDIUM 6.5
- TI-2024-17441 A stored cross-site scripting (XSS) vulnerability in the Edit Content Layout module of… CVSS 3.1MEDIUM 6.1
- TI-2018-10413 An issue was discovered in Kirby 2.5.12. CVSS 3.1MEDIUM 5.4
- TI-2024-17438 Kirby CMS v4.1.0 was discovered to contain a reflected self-XSS vulnerability via the URL parameter. CVSS 3.1MEDIUM 4.7
Sources
- CVE-2026-41325 · CVE Program
- CVE-2026-41325 · NVD
- FIRST EPSS
- GHSA-6gqr-mx34-wh8r · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences