GHSA-99G4-59V5-G9CW
Tailor Bulk Import Bypasses Sub-Permission Checks
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-99G4-59V5-G9CW divulgada · CVSS 2.7 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The Tailor bulk action controller validated only a limited blueprint permission on the import path, while the standard entry editor explicitly gates create, publish, update, and delete operations against the corresponding `.create`, `.publish`, and `.delete` sub-permissions. Combined with the `RecordImport` model writing each supplied column directly to the record and honoring `update_existing`, a backend user could reach `/admin/tailor/bulkactions/<slug>/import`, supply data setting `is_enabled` and `published_at`, and publish or overwrite entries without holding the sub-permissions the editor enforces.
Scope of impact is narrow. Exploitation requires authenticated backend access to a Tailor section. Backend users are already trusted with content within their reach; the bypass produces a meaningful privilege gap only in deployments that split base, create, and publish permissions across distinct roles, which is uncommon in default deployments. No confidentiality impact (the user could already read the section) and no path to escalate outside the affected section.
Impact
- A backend user with a limited Tailor sub-permission on a section can reach import operations that the standard editor gates behind higher sub-permissions
- Requires authenticated backend access with at least one sub-permission on the target section
- Bounded to the affected section; no path to data outside that section, no confidentiality impact, no availability impact
Patches
The vulnerability has been patched in v4.2.25. The bulk action controller now enforces the appropriate sub-permission on each action, matching the explicit gating already applied by the entry editor: the base blueprint permission is required to update existing records via `update_existing`, and any `column_match` targeting publication columns (`is_enabled`, `published_at`, `expired_at`) requires `.publish`. The Tailor import config declares the corresponding `import[permissions]` key so the import-specific check is no longer a no-op. `RecordImport` additionally rejects attribute writes that fall outside the model's documented import surface.
Workarounds
If upgrading immediately is not possible:
- Restrict `tailor.entry.<uuid>` and its sub-permissions to users you also intend to grant the full set of `.create`, `.publish`, and `.delete` on the same section
- Restrict access to `/admin/tailor/bulkactions/*` paths at the web server layer for users who should not have bulk import access
References
- Reported by callmeks
- Reported by Return-Zer0
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 |
|---|---|---|---|---|
Packagistoctober/system |
Corregida | 4.2.25 | — | — |
4.2.25Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/octobercms/october/security/advisories/GHSA-99g4-59v5-g9cwLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
