Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-21896: CWE-863: Incorrect Authorization in getkirby kirby

0
Medium
VulnerabilityCVE-2026-21896cvecve-2026-21896cwe-863
Published: Thu Jan 08 2026 (01/08/2026, 18:09:10 UTC)
Source: CVE Database V5
Vendor/Project: getkirby
Product: kirby

Description

Kirby is an open-source content management system. From versions 5.0.0 to 5.2.1, Kirby is missing permission checks in the content changes API. This vulnerability affects all Kirby sites where user permissions are configured to prevent specific role(s) from performing write actions, specifically by disabling the update permission with the intent to prevent modifications to site content. This vulnerability does not affect those who have not altered the deviated from default user permissions. This issue has been patched in version 5.2.2.

AI-Powered Analysis

AILast updated: 01/08/2026, 18:32:09 UTC

Technical Analysis

CVE-2026-21896 identifies an incorrect authorization vulnerability (CWE-863) in the Kirby content management system, specifically affecting versions 5.0.0 through 5.2.1. Kirby’s content changes API fails to properly enforce permission checks when user roles are customized to restrict write actions, such as disabling the update permission to prevent content modifications. This flaw allows users with limited privileges—who should not be able to update content—to bypass these restrictions and perform unauthorized write operations. The vulnerability arises from missing or insufficient authorization logic in the API handling content changes, which deviates from the intended access control model. Exploitation requires the attacker to have at least low-level privileges (authenticated user with limited write permissions) and some user interaction, but does not require elevated privileges or complex attack techniques. The vulnerability does not impact installations that retain default user permission settings, as the issue is tied to customized roles. The vendor addressed the issue in Kirby version 5.2.2 by adding the necessary permission checks to the content changes API. The CVSS 4.0 base score of 5.8 reflects a medium severity, considering network attack vector, low attack complexity, partial authentication, user interaction, and high impact on integrity with limited impact on availability and confidentiality. No known exploits have been reported in the wild to date.

Potential Impact

For European organizations using Kirby CMS versions between 5.0.0 and 5.2.1 with customized user roles restricting write permissions, this vulnerability poses a risk of unauthorized content modification. Such unauthorized changes can undermine the integrity and reliability of website content, potentially damaging organizational reputation, misleading users, or facilitating further attacks such as phishing or misinformation campaigns. While confidentiality and availability impacts are limited, the integrity breach can have significant consequences for public-facing websites, especially for sectors relying on accurate and trustworthy content such as government, media, education, and e-commerce. Organizations that have not customized user permissions or use default settings are not affected. The absence of known exploits reduces immediate risk, but the ease of exploitation and network accessibility mean attackers could leverage this vulnerability if discovered. Compliance with data integrity and security standards may also be impacted if unauthorized content changes occur.

Mitigation Recommendations

The primary mitigation is to upgrade all Kirby CMS installations to version 5.2.2 or later, where the authorization checks have been properly implemented. Organizations should audit their current Kirby versions and prioritize patching those within the affected range (>=5.0.0 and <5.2.2). Additionally, review and tighten user role configurations to minimize unnecessary write permissions and ensure that roles are assigned following the principle of least privilege. Implement monitoring and alerting on content changes to detect unauthorized modifications promptly. Employ web application firewalls (WAFs) with custom rules to detect anomalous API requests targeting content changes endpoints. Conduct regular security assessments and penetration testing focusing on CMS authorization controls. Finally, maintain an inventory of CMS instances and enforce strict update policies to reduce exposure to known vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-05T17:24:36.930Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 695ff65701d35e5d0c7d3f04

Added to database: 1/8/2026, 6:24:23 PM

Last enriched: 1/8/2026, 6:32:09 PM

Last updated: 1/9/2026, 1:13:53 PM

Views: 20

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats