CVE-2026-45334: CWE-862: Missing Authorization in getkirby kirby
Kirby is an open-source content management system. In versions prior to 4.9.1 and 5.4.1, the content-locking feature returned lock information without checking the requesting user's access permissions. Kirby's Panel includes a content-locking feature that records which user currently has a model open for editing. This lock prevents conflicting edits by multiple users and displays the locking user's identity in the Panel UI so other users know who to contact. Internally, the locking user's email address and identifier are included in every Panel view payload and in error responses returned when a user attempts to edit a model that is currently locked by another user. This allowed a low-privilege authenticated Panel user, whose role was configured with users.access: false or users.list: false, to learn the email address and identifier of any user who currently had a model open for editing in the Panel, including administrators and other higher-privilege users. Content locks are active for a configurable window (10 minutes by default). The email address can allow admin account enumeration, target phishing, and feed credential-stuffing attacks against the Kirby installation or other sites. The internal user ID can be cross-referenced with other endpoints once the requester has obtained a higher privilege through unrelated means. This issue has been fixed in versions 4.9.1 and 5.4.1.
AI Analysis
Technical Summary
Kirby's content-locking feature in versions before 4.9.1 and 5.4.1 returned lock information without verifying the requesting user's access permissions. This allowed low-privilege authenticated Panel users, even those with restricted user access roles, to obtain email addresses and internal user IDs of users who currently have content locked for editing, including administrators. The vulnerability is classified as CWE-862 (Missing Authorization). The exposure window corresponds to the content lock duration (default 10 minutes). This information leakage can aid in admin account enumeration and targeted attacks. The vulnerability was addressed in Kirby versions 4.9.1 and 5.4.1.
Potential Impact
Low-privilege authenticated users can access sensitive information (email addresses and user IDs) of higher-privilege users currently editing content. This information leakage can facilitate admin account enumeration, targeted phishing campaigns, and credential-stuffing attacks against the Kirby installation or other sites. However, it does not directly allow privilege escalation or unauthorized content modification. The exposure is limited to the content lock duration (default 10 minutes).
Mitigation Recommendations
This vulnerability has been fixed in Kirby versions 4.9.1 and 5.4.1. Users should upgrade to these or later versions to remediate the issue. Patch status is not explicitly stated but the fix versions are known; therefore, upgrading to 4.9.1 or 5.4.1 or newer is the recommended remediation. No vendor advisory content contradicts this guidance.
CVE-2026-45334: CWE-862: Missing Authorization in getkirby kirby
Description
Kirby is an open-source content management system. In versions prior to 4.9.1 and 5.4.1, the content-locking feature returned lock information without checking the requesting user's access permissions. Kirby's Panel includes a content-locking feature that records which user currently has a model open for editing. This lock prevents conflicting edits by multiple users and displays the locking user's identity in the Panel UI so other users know who to contact. Internally, the locking user's email address and identifier are included in every Panel view payload and in error responses returned when a user attempts to edit a model that is currently locked by another user. This allowed a low-privilege authenticated Panel user, whose role was configured with users.access: false or users.list: false, to learn the email address and identifier of any user who currently had a model open for editing in the Panel, including administrators and other higher-privilege users. Content locks are active for a configurable window (10 minutes by default). The email address can allow admin account enumeration, target phishing, and feed credential-stuffing attacks against the Kirby installation or other sites. The internal user ID can be cross-referenced with other endpoints once the requester has obtained a higher privilege through unrelated means. This issue has been fixed in versions 4.9.1 and 5.4.1.
CVSS v4.0
Score 5.3medium
Affected software
pkg:github/getkirby/kirbyRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kirby's content-locking feature in versions before 4.9.1 and 5.4.1 returned lock information without verifying the requesting user's access permissions. This allowed low-privilege authenticated Panel users, even those with restricted user access roles, to obtain email addresses and internal user IDs of users who currently have content locked for editing, including administrators. The vulnerability is classified as CWE-862 (Missing Authorization). The exposure window corresponds to the content lock duration (default 10 minutes). This information leakage can aid in admin account enumeration and targeted attacks. The vulnerability was addressed in Kirby versions 4.9.1 and 5.4.1.
Potential Impact
Low-privilege authenticated users can access sensitive information (email addresses and user IDs) of higher-privilege users currently editing content. This information leakage can facilitate admin account enumeration, targeted phishing campaigns, and credential-stuffing attacks against the Kirby installation or other sites. However, it does not directly allow privilege escalation or unauthorized content modification. The exposure is limited to the content lock duration (default 10 minutes).
Mitigation Recommendations
This vulnerability has been fixed in Kirby versions 4.9.1 and 5.4.1. Users should upgrade to these or later versions to remediate the issue. Patch status is not explicitly stated but the fix versions are known; therefore, upgrading to 4.9.1 or 5.4.1 or newer is the recommended remediation. No vendor advisory content contradicts this guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-11T20:50:30.540Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59dfe668715ace439a8d51
Added to database: 07/17/2026, 07:55:18 UTC
Last enriched: 07/17/2026, 07:56:23 UTC
Last updated: 08/31/2026, 11:10:31 UTC
Views: 71
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.