GHSA-C684-H96H-X6G9
Media picker listing, navigation and selection aren't scoped to the field's restrictions
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-C684-H96H-X6G9 divulgada · CVSS 4.3 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
Several parts of the media picker ignore the restrictions configured on the field. None of them needs any request tampering:
- Wildcard types: a wildcard accepted type such as `image/*` is added to the listing query with an ungrouped `orWhere`. Matching images from every directory and disk, and from every tenant without Filament's tenant scope, are listed and can be selected.
- `limitToDirectory()`: this only affects search and the starting folder. The breadcrumbs, which are always shown, and directory navigation can reach any folder.
- Search: search ignores the accepted file types.
- Directory list: the directory list isn't scoped to the disk or tenant, so other tenants' folder names are disclosed.
- Disk: the file listing doesn't filter by disk.
- Saved ids: these aren't checked for existence, tenant or type. When Filament's tenant scope isn't applied, saving another tenant's media id and reloading the form discloses that record.
Exploiting this needs an account that can open a picker.
*Score:* `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N` (4.3)
Affected versions
Confirmed at runtime on 5.5.0 and 3.7.11. 4.2.1 was checked against the 5.x code paths, which are the same, and the fixes were tested on every line.
All 5.x and 4.x releases are affected.
On 3.x only some parts apply: search ignores accepted types, there's no disk filter, and saved ids aren't checked.
- Wildcard query: it is grouped correctly in 3.7.11, though some earlier 3.x releases left it ungrouped.
- Directory restriction: 3.x has no directory navigation, so it can't be escaped that way.
Patches
Upgrade to 5.5.3, 4.2.3 or 3.7.13.
What the picker now checks
Everything the picker and its media panel read goes through one scoped query:
- Where it applies: listing, search, folders, navigation, insert, item actions and saved values.
- What it checks:
- the field's disk;
- the tenant;
- the accepted types, with wildcards grouped correctly and never matching scriptable types;
- `limitToDirectory()`, which covers the folder and its subfolders.
- New selections: a selection outside the field's settings fails validation.
Previously saved media
Media already saved on a record keeps loading as long as it exists and belongs to the tenant. That includes pickers nested in Repeaters, Builders and Groups, which read only from their own place in the column.
Pickers inside conditionally visible components fall back to the strict rule.
Workarounds
Avoid wildcard accepted types. Register `CuratorPlugin` on tenant panels so Filament's tenant scope applies, and don't rely on `limitToDirectory()` as an access control.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Packagistawcodes/filament-curator |
Corregida | 3.7.13, 4.2.3, 5.5.3 | — | — |
3.7.134.2.35.5.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/awcodes/filament-curator/security/advisories/GHSA-c684-h96h-x6g9Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
