Dev.to Security 🔐 Cybersecurity 👁 0 📖 3 min read

CVE-2026-69138: CVE-2026-69138: Authorization Bypass Through User-Controlled Key and Missing Authorization in…

CVE-2026-69138: Authorization Bypass Through User-Controlled Key and Missing Authorization in djangocms-versioning Vulnerability ID: CVE-2026-69138 CVSS Score: 6.5 Published: 2026-11-18 An authorization bypass and b

CVE-2026-69138: Authorization Bypass Through User-Controlled Key and Missing Authorization in djangocms-versioning

Vulnerability ID: CVE-2026-69138
CVSS Score: 6.5
Published: 2026-11-18

An authorization bypass and broken object-level access control vulnerability exists in djangocms-versioning prior to version 2.6.1. The check_discard and check_edit_redirect condition pipelines on the Version model omitted the user_can_change permission predicate. Because the corresponding administrative views retrieve target versions directly by their URL primary key and depend entirely on these condition pipelines for object-level access control, authenticated staff users without per-object change permissions can permanently delete draft versions or spawn new draft versions from published content.

TL;DR

Authenticated staff users in djangocms-versioning prior to 2.6.1 can bypass object-level permissions via the discard_view and edit_redirect_view administrative endpoints. By supplying arbitrary version primary keys, an unauthorized staff user can permanently delete draft content objects or generate editable drafts from restricted published content.

Technical Details

  • CVE ID: CVE-2026-69138 (GHSA-5g9x-qwh5-33x4)
  • CWE Classification: CWE-639 (Authorization Bypass Through User-Controlled Key) / CWE-862 (Missing Authorization)
  • CVSS v3.1 Score: 6.5 Medium (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H)
  • Attack Vector: Network (Authenticated Staff HTTP POST to VersionAdmin endpoints)
  • Affected Component: djangocms_versioning.models.Version (check_discard & check_edit_redirect)
  • Security Impact: Permanent deletion of arbitrary draft content objects and unauthorized creation of drafts from published content
  • Patched Version: djangocms-versioning 2.6.1
  • CISA KEV Status: Not Listed

Affected Systems

  • django-cms/djangocms-versioning
  • djangocms-versioning: < 2.6.1 (Fixed in: 2.6.1)

Code Analysis

Commit: d8c570d

fix: Enforced change permission on discard and edit_redirect (#573)

--- a/djangocms_versioning/models.py
+++ b/djangocms_versioning/models.py
@@ -32,6 +32,7 @@
 not_draft_error = _("This version is not a draft: to make changes create a new draft")
 lock_error_message = _("The latest version is locked by {user}")
 lock_draft_error_message = _("The draft version is locked by {user}")
+change_permission_error = _("You do not have change permissions")
 permission_error_message = _("You do not have permission to perform this action")


@@ -305,7 +306,7 @@ def copy(self, created_by):

     check_archive = Conditions(
         [
-            user_can_change(_("You do not have change permissions")),
+            user_can_change(change_permission_error),
             in_state([constants.DRAFT], _("Version is not in draft state")),
             is_not_locked(lock_error_message),
         ]
@@ -525,7 +526,7 @@ def _has_permission(self, perm: str, user) -> bool:
     )
     check_revert = Conditions(
         [
-            user_can_change(_("You do not have change permissions")),
+            user_can_change(change_permission_error),
             in_state(
                 [constants.ARCHIVED, constants.UNPUBLISHED],
                 _("Version is not in archived or unpublished state"),
@@ -536,6 +537,7 @@ def _has_permission(self, perm: str, user) -> bool:
     check_discard = Conditions(
         [
             in_state([constants.DRAFT], not_draft_error),
+            user_can_change(change_permission_error),
             is_not_locked(lock_error_message),
         ]
     )
@@ -545,6 +547,7 @@ def _has_permission(self, perm: str, user) -> bool:
                 [constants.DRAFT, constants.PUBLISHED],
                 _("Version is not in draft or published state"),
             ),
+            user_can_change(change_permission_error),
             draft_is_not_locked(lock_draft_error_message),
         ]
     )

Commit: 9adfb42

Release 2.6.1 commit

Mitigation Strategies

  • Upgrade djangocms-versioning to version 2.6.1 or later to enforce user_can_change predicates on discard and edit_redirect transitions.
  • Audit all Django user accounts with is_staff=True and revoke staff access from accounts that do not require administrative dashboard access.
  • Enable CMS_PERMISSION = True in Django settings if granular per-object permission boundaries are required across editorial teams.
  • Monitor administrative access logs and WAF telemetry for sequential HTTP POST requests targeting /discard/ and /edit_redirect/ endpoints.

Remediation Steps:

  1. Update project dependencies in requirements.txt or pyproject.toml to specify djangocms-versioning>=2.6.1.
  2. Run pip install --upgrade "djangocms-versioning>=2.6.1" in the deployment environment.
  3. Restart the Django WSGI/ASGI application worker processes to load the patched Version model definitions.
  4. Verify the installation by confirming that unprivileged staff accounts receive the 'You do not have change permissions' error message when attempting to discard or edit-redirect unauthorized versions.

References

Read the full report for CVE-2026-69138 on our website for more details including interactive diagrams and full exploit analysis.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.