CVE-2026-69138: django-cms djangocms-versioning · Insecure Direct Object Reference
Affects django-cms djangocms-versioningSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.6.1 when convenient.
Data as of 18 Nov 2026, 20:49 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 2.6.1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:HExploitation 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 django-cms djangocms-versioning to 2.6.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| django-cmsdjangocms-versioning | Affected
| Fixed in
|
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.
References
- github.com/django-cms/djangocms-versioning/security/advisories/GHSA-5g9x-qwh5-33x4 (opens in a new tab)
- github.com/django-cms/djangocms-versioning/pull/573 (opens in a new tab)
- github.com/django-cms/djangocms-versioning/commit/d8c570daa5f7805e8be51f15545fe77b24c44daf (opens in a new tab)
- github.com/django-cms/djangocms-versioning/releases/tag/2.6.1 (opens in a new tab)