GHSA-8R9G-HHM3-5JFH
Access permissions are not checked when the `files`, `pages` and `users` fields resolve their stored value
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-8R9G-HHM3-5JFH divulgada · CVSS 7.1 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
TL;DR
This vulnerability affects all Kirby sites that rely on blueprint permissions to keep some pages, files or users hidden from certain roles, and that might have potential attackers in that group of authenticated Panel users.
The attack requires a Panel user with update permission on any one model that carries a `files`, `pages` or `users` field.
Sites on which every Panel user may see all content are *not* affected.
This vulnerability is of high severity for affected sites.
----
Affected components
The `files`, `pages` and `users` fields resolve the IDs stored in the content file back into models whenever a Panel view is built. In affected releases that lookup was not checked against the `access` and `list` permissions, although browsing the very same field through its picker was.
Two further Panel surfaces shared the gap: the position fields in the `changeSort` and `changeStatus` dialogs, which listed sibling pages and files, and the breadcrumbs of pages and files, which listed ancestors.
Impact
A Panel user could write the ID of any page, file or user into a field they are allowed to update, and read the resolved model back from the ordinary Panel response, whatever the permissions on that model are. The field's own `query` restriction was not consulted either.
For pages and users this disclosed titles, UUIDs, usernames and email addresses that the role has no access to. For files it also disclosed the media URL, which carries the token that authorizes access to the file.
Nothing here changes the attacker's own permissions, and no content is written to a model they could not already update.
Patches
The problem has been patched in Kirby 5.6.0 https://github.com/getkirby/kirby/releases/tag/5.6.0 and Kirby 4.9.6 https://github.com/getkirby/kirby/releases/tag/4.9.6.
In these releases, the `files`, `pages` and `users` fields check every resolved model against the same predicate their pickers use. A model the current user may not list is replaced with a redacted placeholder that carries nothing but the ID already stored in the content file, so that saving the model does not drop the entry. The position fields and the breadcrumbs redact inaccessible entries in the same way.
How this differs from CVE-2026-108924
CVE-2026-108924 describes an authorization bypass in `OptionsQuery::resolve` in `src/Option/OptionsQuery.php` (Dynamic Option Generation). This advisory is a different defect in a different component:
- Affected code. The `files`, `pages` and `users` fields resolve their stored value without an `isListable()` check, in `config/fields/files.php`, `pages.php` and `users.php`. Nothing under `src/Option/` is involved.
- Fix. 4.9.6 and 5.6.0 change `config/fields/files.php`, `pages.php`, `users.php` and `config/fields/mixins/picker.php`. `src/Option/OptionsQuery.php` is byte-identical between 4.9.5 and 4.9.6, and between 5.5.3 and 5.6.0, so the release that fixes this advisory does not touch the code CVE-2026-108924 describes.
- References. The CVE-2026-108924 record lists this advisory among its references, but its description does not match this advisory's affected code or its fix.
Credits
Thanks to Eurico Nicacio (@euriconicacio) for responsibly reporting the identified issue.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Packagistgetkirby/cms |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/getkirby/kirby/security/advisories/GHSA-8r9g-hhm3-5jfhLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
