GHSA-X6QC-FV74-F8R2
Paste-a-copy IDOR discloses unauthorized plugin content
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.10 | django-cms · -5 d desde divulgación | |
| Divulgación | Publicada | GHSA-X6QC-FV74-F8R2 divulgada · CVSS 6.5 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
The `move_plugin` admin endpoint copies an arbitrary plugin's content into a placeholder the requester controls, without checking the requester's permission on the placeholder the plugin is copied from. Any staff user can read the content of any plugin in the installation, including pages, sites and clipboards they have no access to.
This is the same class of issue as GHSA-4xfr-4p46-gc6p, in a second pair of functions that the fix released in 5.0.8 did not cover.
Details
`PlaceholderAdmin.move_plugin()` performs a "paste" instead of a move when the request sets `move_a_copy`. The plugin to paste is resolved from a client-supplied id via `_get_plugin_from_id()`, which performs no authorization of its own, and is then handed to `_paste_plugin()` or `_paste_placeholder()`. Both helpers only checked the *target* placeholder (`has_copy_from_clipboard_permission()` and `Placeholder.check_source()`). Nothing verified that the requester is allowed to read the plugin's own placeholder, or that the plugin came from their clipboard at all — which is the only operation these helpers exist for.
A second, contributing issue: `UserSettings.has_placeholder_change_permission()` and `PlaceholderForeignKey.run_checks()` granted every user permission on *every* clipboard, not only their own. Clipboards are per-user and may hold content other users must not see.
Two variants were confirmed against the `move-plugin` endpoint:
- Any plugin. With `plugin_id` pointing at a plugin in a restricted placeholder and `placeholder_id` pointing at a placeholder the attacker controls, the plugin and its descendants are copied verbatim into the attacker's placeholder and persisted there.
- Any other user's clipboard. With `plugin_id` pointing at the `PlaceholderPlugin` in another user's clipboard, that clipboard's contents are copied into the attacker's own.
The attacker's own clipboard is always a valid target, since a user may always write to it. No per-page or per-placeholder permission configuration is required for the attack to work.
## Impact
A staff user holding the Django `add` permission for a plugin model can exfiltrate the content of any plugin of that type anywhere in the installation — other pages, other sites, other users' clipboards — regardless of page, placeholder or object permissions. The copied plugins persist in a placeholder the attacker controls and remain readable through the normal edit and preview UI.
Exploitation requires an authenticated staff account. It does *not* require `CMS_PERMISSION=True` or any per-page permission setup. Integrity and availability are not affected: the copies are only written to placeholders the attacker is already allowed to write to.
## Patches
- django CMS 5.0.10
- django CMS 5.1.1
The fix adds a source-side authorization check to both paste helpers, via a new overridable `PlaceholderAdmin.has_paste_from_source_permission()` hook, and restricts clipboard permissions to the clipboard's owner.
Projects that override `_paste_plugin()` or `_paste_placeholder()` in a custom placeholder admin must apply the same source-side check.
Workarounds
There is no configuration-level workaround; upgrade to a patched release. Until then, limit staff accounts to trusted users, and note that granting a user the `add` permission for any plugin model effectively grants read access to every plugin of that type in the installation.
References
- Related advisory: GHSA-4xfr-4p46-gc6p (Clipboard copy IDOR discloses unauthorized plugin
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 |
|---|---|---|---|---|
pypidjango-cms |
Corregida | 5.0.10 | -5 d | 5.1.3 no afectada |
5.0.10Arsenal 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-x6qc-fv74-f8r2Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
