Skip to main content
Menu
CVEs

CVE

djangocms-versioning authorization bypass in version management

CVE-2026-69138Published Updated Summary written by a model

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.6.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.6.1.

Summary

The djangocms-versioning package from django-cms has an authorization bypass that lets a staff user delete a draft version and its content, or create an editable draft from a published version, without permission to change that specific content object. The bug can be reached remotely, but only after logging in with a high-privilege account.

Original description

djangocms-versioning is a general-purpose versioning package for django CMS 4 and later. Prior to 2.6.1, the check_discard and check_edit_redirect Conditions on djangocms_versioning.models.Version omit user_can_change, while VersionAdmin.discard_view and VersionAdmin.edit_redirect_view obtain a version by its primary key and rely on those conditions for object-level authorization. With CMS_PERMISSION set to True, the affected views are gated only by is_staff, allowing any staff user to select content without object-level change permission. With the default CMS_PERMISSION value of False, a staff user must also hold the global Django change_ permission, but that model-level permission does not enforce the intended per-object authorization, so the user can delete a draft version and its content object through discard or create an editable draft from a published version through edit_redirect even when the user cannot change that specific content object. This issue is fixed in version 2.6.1.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • 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
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 2.6.1.

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-69138 (djangocms-versioning: Authorization Bypass Through User-Controlled Key and Missing Authorization), 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-69138 (entry last updated 2026-11-18):
Affected:
- django-cms djangocms-versioning: fixed in 2.6.1
Fixed versions: 2.6.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-69138 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69138 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-versioning/security/advisories/GHSA-5g9x-qwh5-33x4
- https://github.com/django-cms/djangocms-versioning/pull/573
- https://github.com/django-cms/djangocms-versioning/commit/d8c570daa5f7805e8be51f15545fe77b24c44daf
- https://github.com/django-cms/djangocms-versioning/releases/tag/2.6.1
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-69138
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-69138"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • django-cms djangocms-versioning

    fixed in 2.6.1

Evidence 6

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-69138

Is CVE-2026-69138 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-69138?

djangocms-versioning: before 2.6.1.Source: cve.now feed data

How do I fix CVE-2026-69138?

Upgrade to a fixed version: 2.6.1.Source: cve.now feed data

More CVEs