CVE-2026-40099: CWE-863: Incorrect Authorization in getkirby kirby
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.
AI Analysis
Technical Summary
Kirby CMS uses user role permissions to control actions on content models, including page creation and status changes. Prior to versions 4.9.0 and 5.4.0, the 'pages.changeStatus' permission was not enforced during page creation via the REST API, allowing authenticated users with 'pages.create' permission to create pages already published by overriding the 'isDraft' flag. This bypasses the normal editorial process where new pages are created as drafts and require publishing separately. The vulnerability is classified as CWE-863 (Incorrect Authorization). The issue was patched by adding a check that restricts page creation of published pages to users with the 'pages.changeStatus' permission.
Potential Impact
Authenticated users with the 'pages.create' permission could bypass the editorial workflow by creating published pages directly through the REST API, potentially leading to unauthorized content publication. This could affect content integrity and editorial control within the CMS. The vulnerability does not allow privilege escalation beyond the assigned permissions but weakens the intended authorization model for page publication.
Mitigation Recommendations
Upgrade Kirby CMS to version 4.9.0 or later if using the 4.x branch, or to version 5.4.0 or later if using the 5.x branch, where this vulnerability has been fixed. The fix enforces the 'pages.changeStatus' permission during page creation to prevent unauthorized publishing. Since no official patch link or advisory is provided, verify the upgrade availability and instructions from the official Kirby project resources. Patch status is not explicitly confirmed beyond the version fixes; check vendor advisories for the latest remediation guidance.
CVE-2026-40099: CWE-863: Incorrect Authorization in getkirby kirby
Description
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.
CVSS v4.0
Score 5.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kirby CMS uses user role permissions to control actions on content models, including page creation and status changes. Prior to versions 4.9.0 and 5.4.0, the 'pages.changeStatus' permission was not enforced during page creation via the REST API, allowing authenticated users with 'pages.create' permission to create pages already published by overriding the 'isDraft' flag. This bypasses the normal editorial process where new pages are created as drafts and require publishing separately. The vulnerability is classified as CWE-863 (Incorrect Authorization). The issue was patched by adding a check that restricts page creation of published pages to users with the 'pages.changeStatus' permission.
Potential Impact
Authenticated users with the 'pages.create' permission could bypass the editorial workflow by creating published pages directly through the REST API, potentially leading to unauthorized content publication. This could affect content integrity and editorial control within the CMS. The vulnerability does not allow privilege escalation beyond the assigned permissions but weakens the intended authorization model for page publication.
Mitigation Recommendations
Upgrade Kirby CMS to version 4.9.0 or later if using the 4.x branch, or to version 5.4.0 or later if using the 5.x branch, where this vulnerability has been fixed. The fix enforces the 'pages.changeStatus' permission during page creation to prevent unauthorized publishing. Since no official patch link or advisory is provided, verify the upgrade availability and instructions from the official Kirby project resources. Patch status is not explicitly confirmed beyond the version fixes; check vendor advisories for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-09T01:41:38.536Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69eac1fc87115cfb688c86f2
Added to database: 4/24/2026, 1:06:04 AM
Last enriched: 5/1/2026, 8:39:58 PM
Last updated: 6/7/2026, 8:27:08 AM
Views: 72
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.