- Severity: MEDIUM
- CVE: CVE-2026-69139
- Ecosystems: pip
- Packages: djangocms-moderation
## 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 specifi…
Source: GitHub Security Advisories · 2026-11-19