A GitHub Advisory Database entry published on 19 November 2026 describes a flaw in djangocms-moderation, a Django package, that exposes moderation comments to staff users who are not participants. The advisory is tracked as GHSA-pj7p-238h-76pv and CVE-2026-69139. [1]
According to the advisory, the Django admin views for collection and request comments check only the object id supplied in the URL and the model-level view permission. They do not apply the participant check, which covers the author and assigned moderators, that already existed in the codebase. Write actions were already restricted to the author. [1]
Any authenticated staff user holding the comment view permission can, by supplying a target id, read the comments of a collection or moderation request they are not part of. The changelists are limited to one object at a time, but the advisory says comment text appears in the changelist HTML and on the individual change page, so specific threads can be reached by iterating ids. [1]
The advisory lists the affected package as djangocms-moderation versions 2.3.0 and earlier. Its affected-package field gives 2.4.0 as the fixed release, while its remediation section recommends upgrading to 2.4.1. The two versions are not reconciled in the advisory. [1]
Until an upgrade is applied, the advisory suggests restricting the view permissions for collection and request comments to trusted users and avoiding granting them across teams that should not see each other's comments. The advisory states this does not fully close the issue. [1]
GitHub rates the issue medium severity with a CVSS score of 4.3. That is the advisory publisher's assessment, and TechDots has not independently verified it. [1]
The advisory is the only source reviewed for this report. The information above reflects its claims and has not been confirmed by the package maintainers or by independent testing. [1]