Medium

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

  • Disclosed: 19.11.2026
  • Updated: 20.11.2026 10:00

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.

What to do

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) djangocms-moderation < 2.4.0 2.4.0

References

CVSS score 4.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-200, CWE-639, CWE-862
Platform
Python (PyPI)
Package
djangocms-moderation
Disclosed
19.11.2026
Updated
20.11.2026 10:00

Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.

OSV / GitHub Advisory Database - GHSA-pj7p-238h-76pv - CC BY 4.0

Vulnerability history: djangocms-moderation

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

This is the only known vulnerability of this package.

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.