Kirby: Content locks disclose IDs and emails of inaccessible users from `users.access/list` permissions
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-862.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- 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.1; 5.0.0 to before 5.4.1 | 4.9.1, 5.4.1 | Patch available | CNA |
| — | getkirby/cms (Packagist) | before 4.9.1 | 4.9.1 | Patch available | GHSA-39vq-49qm-r2mc |
| — | getkirby/cms (Packagist) | 5.0.0 to before 5.4.1 | 5.4.1 | Patch available | GHSA-39vq-49qm-r2mc |
- kirby Vendorgetkirby Affected before 4.9.1; 5.0.0 to before 5.4.1 Fixed in 4.9.1, 5.4.1 Patch available CNA
- getkirby/cms (Packagist) Vendor— Affected before 4.9.1 Fixed in 4.9.1 Patch available GHSA-39vq-49qm-r2mc
- getkirby/cms (Packagist) Vendor— Affected 5.0.0 to before 5.4.1 Fixed in 5.4.1 Patch available GHSA-39vq-49qm-r2mc
Remediation
- Fix · CNA kirby (getkirby) Fixed in 4.9.1, 5.4.1
- Fix · GHSA-39vq-49qm-r2mc getkirby/cms (Packagist) Fixed in 4.9.1 Advisory →
- Fix · GHSA-39vq-49qm-r2mc getkirby/cms (Packagist) Fixed in 5.4.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-45334
- 2026-10-03 Alias added: GHSA-39vq-49qm-r2mc
References
More getkirby 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-45334 · CVE Program
- CVE-2026-45334 · NVD
- FIRST EPSS
- GHSA-39vq-49qm-r2mc · 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