Skip to content
Threat Brief

← All advisories

CVE-2026-69138

Medium 6.5No known exploitationFix available

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

Vendor advisory: GHSA-5g9x-qwh5-33x4

Record last updated

CVSS score

6.5

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 42% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-639, CWE-862

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
django-cmsdjangocms-versioning< 2.6.1Not documentedCVE Program
pipdjangocms-versioningall versions up to and including 2.6.02.6.1GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references