CVE-2026-69138: djangocms-versioning: Authorization Bypass Through User-Controlled Key and Missing Authorization
The discard and edit_redirect version transitions did not enforce a per-object change-permission check, while the sibling transitions (archive, publish, unpublish, revert) all did. As a result a low-privileged staff user could discard (delete) any draft version — and thereby the underlying content object — of content they have no change permission on, and could create an editable draft off any published version, by supplying a version primary key they should not have access to (an insecure direct object reference).
References
- github.com/advisories/GHSA-5g9x-qwh5-33x4
- github.com/django-cms/djangocms-versioning/commit/d8c570daa5f7805e8be51f15545fe77b24c44daf
- github.com/django-cms/djangocms-versioning/pull/573
- github.com/django-cms/djangocms-versioning/releases/tag/2.6.1
- github.com/django-cms/djangocms-versioning/security/advisories/GHSA-5g9x-qwh5-33x4
- nvd.nist.gov/vuln/detail/CVE-2026-69138
Code Behaviors & Features
Detect and mitigate CVE-2026-69138 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →