Kirby is an open-source content management system. Prior to versions 4.9.0 and 5.4.0, 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). In affected releases, 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 updated the `Options` logic to no longer double-resolve queries in option values coming from `OptionsQuery` or `OptionsApi` sources. Kirby now only resolves queries that are directly configured in the blueprints.
Kirby CMS versions prior to 4.9.0 and 5.4.0 contain an authorization bypass vulnerability where the changeStatus permission is not enforced during page creation, allowing users to publish pages without proper authorization. This affects the permission control mechanism that should restrict which user roles can perform specific actions on content models.
يحتوي نظام إدارة المحتوى Kirby على ثغرة في التحكم بالأذونات حيث لا يتم التحقق من إذن changeStatus بشكل صحيح عند إنشاء صفحات جديدة. يسمح هذا للمستخدمين بنشر الصفحات دون الحصول على الأذونات المطلوبة، مما يؤدي إلى تجاوز آليات التحكم في الوصول.
نظام إدارة المحتوى Kirby في الإصدارات السابقة للإصدار 4.9.0 و 5.4.0 يحتوي على ثغرة تجاوز التفويض حيث لا يتم فرض إذن changeStatus أثناء إنشاء الصفحات. يسمح هذا للمستخدمين بنشر الصفحات دون الحصول على التفويض المناسب.
Update Kirby CMS to version 4.9.0 or 5.4.0 or later immediately. Review and audit all user roles and permissions in your Kirby installation to ensure proper authorization controls are in place. Verify that users without changeStatus permission cannot publish pages.
قم بتحديث نظام Kirby CMS إلى الإصدار 4.9.0 أو 5.4.0 أو أحدث على الفور. راجع وتدقيق جميع أدوار المستخدمين والأذونات في تثبيت Kirby الخاص بك للتأكد من وجود عناصر تحكم التفويض المناسبة. تحقق من أن المستخدمين الذين لا يملكون إذن changeStatus لا يمكنهم نشر الصفحات.