CVE-2026-69138

GHSA-5g9x-qwh5-33x4 · published 18 Nov 2026 · updated 19 Nov 2026

djangocms-versioning: Authorization Bypass Through User-Controlled Key and Missing Authorization

6.5MediumCVSS 6.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in djangocms-versioning 2.6.1.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
django-cms<2.6.1
pypi: djangocms-versioning<2.6.1, <=2.6.02.6.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-69138 severity on Zeptric[![CVE-2026-69138](https://zeptric.io/badge/cve/CVE-2026-69138.svg)](https://zeptric.io/cve/CVE-2026-69138)