GHSA-8RRX-5C4M-WHXC
Missing authorization in django CMS object preview and edit endpoints discloses plugin content of non-PageContent objects
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 5.0.11 | django-cms · -8 d desde divulgación | |
| Remediación | Parche 5.1.2 | django-cms · -8 d desde divulgación | |
| Divulgación | Publicada | GHSA-8RRX-5C4M-WHXC divulgada · CVSS 6.5 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
The frontend-editing object endpoints `render_object_preview` and `render_object_edit` performed no object-level authorization for objects that are not `PageContent`. Both are registered through `admin_site.admin_view()`, which only requires an active staff account, so any authenticated, active staff user — including one holding no permissions at all — could render, and therefore read, the full plugin content of any frontend-editable object, without permission to view or change it:
GET /<lang>/admin/cms/placeholder/object/<content_type_id>/preview/<object_id>/
GET /<lang>/admin/cms/placeholder/object/<content_type_id>/edit/<object_id>/Both `content_type_id` and `object_id` are small sequential integers and can be enumerated.
The `PageContent` branch of `render_object_endpoint()` was authorized (via `render_page()` → `user_can_view_page()`), but the branch handling every other frontend-editable model was not. The three checks that did run on that path — `is_editable_model()`, membership in `toolbar_enabled_models`, and `toolbar.object_is_editable()` — are capability and versioning-state checks, not permission checks, and the last is skipped entirely for preview.
This is an incomplete fix for GHSA-8qj2-c6q4-f399. That advisory added `user_can_view_placeholder_source()` to the non-`PageContent` branch of the sibling endpoint `render_object_structure`, but the identical branch in `render_object_endpoint` — which backs both preview and edit — was left unchanged. The endpoints patched here disclose more than the one patched previously: the structure board exposes placeholder and plugin metadata, whereas preview and edit render the object's complete plugin output.
Impact is limited to disclosure. The plugin mutation endpoints (`add_plugin`, `edit_plugin`, `delete_plugin`, `move_plugin`, `clear_placeholder`) enforce change permission independently and correctly deny the same actor, hence `I:N` in the vector.
Deployments are affected if they register a non-`PageContent` model for frontend editing through `cms_toolbar_enabled_models`. This includes common add-ons: for example `djangocms-alias` registers `AliasContent`, whose render function returns a `TemplateResponse` without a permission check of its own. Aliases routinely hold content scoped to particular editors or sites.
Patches
Fixed in django CMS 5.1.2 and 5.0.11, both released 27 August 2026. The non-`PageContent` branch of `render_object_endpoint()` in `cms/views.py` now performs the same object-level view check as the structure endpoint:
else:
content_type_obj = content_type.get_object_for_this_type(pk=object_id)
# Enforce the same object-level view check as the structure endpoint
# (and, for the page branch above, render_page()'s user_can_view_page).
if not user_can_view_placeholder_source(request.user, content_type_obj):
raise Http404Unauthorized users now receive `404`. View permission is required for both endpoints, matching the structure endpoint; mutations remain separately gated by change permission at the plugin endpoints. Regression tests were added in `cms/tests/test_views.py` (`NonPageContentObjectEndpointTests`).
Upgrade paths:
- 5.1.x → upgrade to 5.1.2 or later.
- 5.0.x → upgrade to 5.0.11 or later.
- 4.1.x and earlier are no longer supported and will not receive a fix. These releases are also missing the fix for GHSA-8qj2-c6q4-f399. Users still on 4.x must upgrade to a supported 5.x release.
Workarounds
None. The affected endpoints are required for frontend editing and cannot be safely disabled or restricted through configuration. Upgrade to django CMS 5.1.2 or 5.0.11.
References
- Fix: https://github.com/django-cms/django-cms/pull/8794
- 5.0.x backport: https://github.com/django-cms/django-cms/pull/8809
- CWE-862: Missing Authorization
- GHSA-8qj2-c6q4-f399 — the sibling structure endpoint; this advisory completes that fix
For more information
If you have any questions or comments about this advisory, email us at security@django-cms.org.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypidjango-cms |
Corregida | 5.0.11, 5.1.2 | -8 d · -8 d | 5.1.3 no afectada |
5.0.115.1.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/django-cms/django-cms/security/advisories/GHSA-8rrx-5c4m-whxcLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
