Skip to main content
VulnerabilityPublished

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

Affects djangocms-versioningSource GCVE Database

0
Compare
Authoritative record:CVE-2026-69138· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.6.1 when convenient.

Data as of 19 Nov 2026, 00:22 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.5
Patch
Available – fixed in 2.6.1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade djangocms-versioning to 2.6.1.

Affected software

ProductAffectedFixed in
PyPIdjangocms-versioningAffected
  • <2.6.1
Fixed in
  • 2.6.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade djangocms-versioning to version 2.6.1 or later, where the vulnerability is fixed by adding the user_can_change condition to the discard and edit_redirect transitions. There is no configuration-only workaround. Until upgrading, restrict staff accounts to trusted users to mitigate risk, as the missing authorization gate reduces to is_staff under CMS_PERMISSION = True.

Description

djangocms-versioning versions prior to 2.6.1 contain an authorization bypass vulnerability where two version state transitions, discard and edit_redirect, do not enforce per-object change permissions. This allows any staff user to discard (delete) draft versions and their underlying content objects or create editable drafts from published versions without proper authorization. The issue arises because these transitions lack the user_can_change condition that other transitions enforce, resulting in broken access control. The vulnerability affects multi-editor deployments with differentiated per-object permissions, reducing authorization to is_staff or a weaker global change permission. The flaw is fixed in version 2.6.1 by adding the missing user_can_change condition to these transitions.

References

Community reviews

Loading reviews…