llamaCVEVulnerability Intelligence
/
Advisory · GitHub · PyPI · djangocms-moderation

GHSA-PJ7P-238H-76PV

djangocms-moderation: Moderation comments disclosed to non-participant staff via the admin changelist

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión2.4.0
Exposición14 hDesde la divulgación, 19 nov 2026, 11:09 a. m.
Detección10 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Monitoreo
Detectada +1
11:09 a. m.
01:02 a. m.
11:09 a. m.
02:37 p. m.
06:05 p. m.
09:34 p. m.
01:02 a. m.
FechaFaseEventoDetalle
Divulgación Publicada GHSA-PJ7P-238H-76PV divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Summary

The Django admin views for moderation comments (`CollectionCommentAdmin` and `RequestCommentAdmin`) render the full comment body but scope access only by an attacker-controlled `id` in the URL and Django's model-level `view_*comment` permission. They perform no per-object participant check. As a result, any authenticated staff user who holds the comment *view* permission can read the comments of any collection or moderation request — including ones they are not a participant of — simply by supplying the target object's id.

Comments are documented and intended to be private to the participants of a collection (its author and the moderators assigned to its workflow). This advisory concerns a read/write authorization asymmetry: the write paths already enforced `request.user == obj.author`, but the read paths did not enforce any participant check.

Details

`ModerationRequest.user_can_view_comments()` — the gate intended to protect comment reads (author or assigned moderator) — existed in the codebase but was never called by the comment admins. Neither `CollectionCommentAdmin` nor `RequestCommentAdmin` overrode `get_queryset`, and their `changelist_view` / `changeform_view` methods resolved the target object directly from the user-supplied id without an authorization check.

The changelists are hard-scoped to a single collection / moderation request (they `raise Http404` when no id is present), so the exposure is not "all comments at once," but any specific collection's or request's comments can be retrieved by iterating ids.

  • `list_display` on both admins includes the comment `message`, so the full body is disclosed directly in the changelist HTML.
  • The individual changeform (`.../<id>/change/`) discloses the same content via a direct URL.

Impact

  • Type: Information disclosure / broken object-level authorization (IDOR).
  • Confidentiality: Comment contents of collections/requests the user does not participate in are exposed. This can include sensitive internal editorial discussion.
  • Integrity / Availability: No impact — comment creation, editing, and deletion already enforced author checks and are unaffected.
  • Who is affected: Deployments where more than one team/group of staff reviewers holds the `view_collectioncomment` / `view_requestcomment` permission. A reviewer of collection A can read the comments of collection B.

Workarounds

Restrict the `view_collectioncomment` and `view_requestcomment` model permissions to trusted users only, and avoid granting them across teams that must not see each other's moderation comments. This does not fully close the issue but reduces the set of users who can exploit it. Upgrading is the only complete fix.

Remediation

Upgrade to djangocms-moderation 2.4.1.

The fix adds a `user_can_view_comments` participant gate (author or assigned moderator) to both comment admins, enforced in `changelist_view` and `changeform_view` for both the collection and request comment models. A `ModerationCollection.user_can_view_comments()` method was added to mirror the existing `ModerationRequest.user_can_view_comments()`. Non-participants now receive an HTTP 403 (`PermissionDenied`).

Credit

Reported via coordinated disclosure.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida
djangocms-moderation< 2.4.0
2.4.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
PyPIdjangocms-moderation
Corregida 2.4.0 — —
Versiones corregidas2.4.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-69139
Otrahttps://github.com/django-cms/djangocms-moderation/security/advisories/GHSA-pj7p-238h-76pv
Otrahttps://github.com/django-cms/djangocms-moderation/pull/374
Otrahttps://github.com/django-cms/djangocms-moderation/commit/a044d9c98c127454b73e8a8ada6e59aaa0a8f621
Otrahttps://github.com/django-cms/djangocms-moderation
Otrahttps://github.com/django-cms/djangocms-moderation/releases/tag/2.4.0

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.