CVE-2026-69139: djangocms-moderation · Moderation comments disclosed to non-participant staff via the admin changelist
Affects djangocms-moderationSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.4.0 when convenient.
Data as of 19 Nov 2026, 17:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 2.4.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade djangocms-moderation to 2.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIdjangocms-moderation | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade djangocms-moderation to version 2.4.0 or later, which adds participant checks to the comment admin views and denies access to non-participants with HTTP 403. As a temporary workaround, restrict the view_collectioncomment and view_requestcomment model permissions to trusted users only and avoid granting them across teams that should not see each other's moderation comments. This workaround reduces exposure but does not fully fix the issue.
Description
A vulnerability in djangocms-moderation before version 2.4.0 allows authenticated staff users with comment view permissions to read moderation comments of collections or requests they are not participants of. The flaw is due to missing per-object participant checks in the admin views, exposing sensitive editorial comments. The issue is fixed in version 2.4.0 by enforcing participant checks and returning HTTP 403 for unauthorized access.
References
- github.com/django-cms/djangocms-moderation/security/advisories/GHSA-pj7p-238h-76pv (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-69139 (opens in a new tab)
- github.com/django-cms/djangocms-moderation/pull/374 (opens in a new tab)
- github.com/django-cms/djangocms-moderation/commit/a044d9c98c127454b73e8a8ada6e59aaa0a8f621 (opens in a new tab)
- github.com/django-cms/djangocms-moderation (opens in a new tab)
- github.com/django-cms/djangocms-moderation/releases/tag/2.4.0 (opens in a new tab)