CVE-2026-69138
Received Received - Intake

Incorrect Object-Level Authorization in django CMS Versioning Prior to 2.6.1

Vulnerability report for CVE-2026-69138, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in djangocms-versioning versions before 2.6.1 allows unauthorized users to delete draft versions or create editable drafts from published versions by exploiting missing object-level permission checks. The discard and edit_redirect actions did not enforce per-object change permissions, enabling low-privileged staff users to perform these actions by supplying version primary keys they should not access.

Detection Guidance

To detect this vulnerability, check the installed version of djangocms-versioning. Run: pip show djangocms-versioning. If the version is 2.6.0 or earlier, the system is vulnerable. Upgrade to version 2.6.1 or later immediately.

Impact Analysis

Unauthorized users could delete draft versions and their underlying content objects or create editable drafts from published content. This affects content integrity and availability, potentially leading to data loss or unauthorized modifications. The impact severity depends on CMS_PERMISSION settings but allows privilege escalation in both default and custom configurations.

Compliance Impact

This vulnerability could lead to unauthorized data deletion or modification, violating integrity and availability requirements in GDPR and HIPAA. Unauthorized changes may result in non-compliance with access control and data protection provisions, potentially leading to regulatory penalties or breaches of confidentiality.

Mitigation Strategies

Upgrade djangocms-versioning to version 2.6.1 or later to enforce proper change permissions for discard and edit_redirect actions.

  • Restrict staff accounts to trusted users only until the upgrade is completed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-69138. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...