CVE
djangocms-moderation moderation comment disclosure in admin changelist
- Exploited
- No known exploitation
- Fix
- Fixed in 2.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.4.0.
Summary
The djangocms-moderation package for django-cms lets an authenticated staff user with comment view permission read internal moderation comments from approval workflows they do not take part in, by enumerating collection or moderation-request identifiers in the Django admin. Attackers can reach this remotely over the network with a low-privilege staff login, and it exposes only the confidentiality of editorial discussions, not comment creation, changes, or deletion.
Original description
djangocms-moderation provides an approval workflow mechanism for organizations that require content approval before publication. Prior to 2.4.0, CollectionCommentAdmin and RequestCommentAdmin in the Django admin use changelist_view and changeform_view to scope comment access through caller-controlled object identifiers and model-level view_collectioncomment or view_requestcomment permissions without invoking ModerationRequest.user_can_view_comments() or an equivalent collection participant check. An authenticated staff user with either view permission can enumerate collection or moderation-request identifiers and read full comment messages for workflows they do not participate in. The exposure affects confidentiality of internal editorial discussions; comment creation, modification, and deletion remain protected, and integrity and availability are unaffected. This issue is fixed in version 2.4.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.4.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-69139 (djangocms-moderation: Moderation comments disclosed to non-participant staff via the admin changelist), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-69139 (entry last updated 2026-11-18):
Affected:
- django-cms djangocms-moderation: fixed in 2.4.0
Fixed versions: 2.4.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-69139 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69139 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/django-cms/djangocms-moderation/security/advisories/GHSA-pj7p-238h-76pv
- https://github.com/django-cms/djangocms-moderation/pull/374
- https://github.com/django-cms/djangocms-moderation/commit/a044d9c98c127454b73e8a8ada6e59aaa0a8f621
- https://github.com/django-cms/djangocms-moderation/releases/tag/2.4.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-69139
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69139"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- django-cms djangocms-moderation
fixed in 2.4.0
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · django-cms/djangocms-moderation · Advisory GHSA-pj7p-238h-76pv |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-69139 |
| Record | NVD · CVE-2026-69139 |
| Other links 3 | |
| Repository | GitHub · django-cms/djangocms-moderation · Pull request #374 |
| Repository | GitHub · django-cms/djangocms-moderation · Commit a044d9c9 |
| Repository | GitHub · django-cms/djangocms-moderation · Release 2.4.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-69139
Is CVE-2026-69139 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-69139?
djangocms-moderation: before 2.4.0.Source: cve.now feed data
How do I fix CVE-2026-69139?
Upgrade to a fixed version: 2.4.0.Source: cve.now feed data