CVE-2026-69139 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in djangocms-moderation. A fix is available for djangocms-moderation — see the affected versions and patch details below.
djangocms-moderation: Moderation comments disclosed to non-participant staff via the admin changelist
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-69139.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
djangocms-moderationReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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_displayon both admins includes the commentmessage, 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_requestcommentpermission. 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | djangocms-moderation | all versions | 2.4.0pip install --upgrade 'djangocms-moderation==2.4.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for djangocms-moderation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update djangocms-moderation to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-69139 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-69139 in your dependencies?
Find it across PyPI, including transitive dependencies.