djangocms-versioning: Authorization Bypass Through User-Controlled Key and Missing Authorization (CVE-2026-69138)
Published Last modified Sources: EUVD, OSV, CVE.org, Hersteller
What is affected, what to do
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.
Update Djangocms-versioning to version 2.6.1.
- Affected
- Djangocms-versioning
lt *..2.6.1
- Djangocms-versioning
- Fixed in
- Djangocms-versioning
2.6.1
- Djangocms-versioning
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.5
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
6.5
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: EUVD, OSV, CVE.org, Hersteller
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 62.50 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 6.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.5
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-639, CWE-862
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: ENISA EUVD, OSV (Open Source Vulnerabilities), cvelistv5, GitHub Security Advisories, CVE.org (MITRE), NVD (NIST)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| django-cms | djangocms-versioning |
|
|
| pip | djangocms-versioning |
|
|
| pypi | djangocms-versioning |
|
|
Vendors and products
Weakness classes (CWE)
CWE-639Authorization Bypass Through User-Controlled Key
Base
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.
Entry at MITRE CWE-639CWE-862Missing Authorization
Class
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Entry at MITRE CWE-862
References & sources
- github.comdjango-cms/djangocms-versioning/commit/d8c570daa5f7805e8be51f15…x_refsource_MISC, euvd, web
- github.comdjango-cms/djangocms-versioning/pull/573x_refsource_MISC, euvd, web
- github.comdjango-cms/djangocms-versioning/releases/tag/2.6.1x_refsource_MISC, euvd, web
- github.comdjango-cms/djangocms-versioning/security/advisories/GHSA-5g9x-q…x_refsource_CONFIRM, euvd, web
- github.comdjango-cms/djangocms-versioningpackage
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedGitHub
CVSS V3.1: AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
Weakness type: CWE-639, CWE-862
Description added or changed
New references:- https://github.com/django-cms/djangocms-versioning/commit/d8c570daa5f7805e8be51f15545fe77b24c44daf
- https://github.com/django-cms/djangocms-versioning/pull/573
- https://github.com/django-cms/djangocms-versioning/releases/tag/2.6.1
- https://github.com/django-cms/djangocms-versioning/security/advisories/GHSA-5g9x-qwh5-33x4
Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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 added —AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:HWeakness type (CWE) added —CWE-639Weakness type (CWE) added —CWE-862Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/69xxx/CVE-2026-69138.json">CVE-2026-69138</a>Reference added —https://github.com/django-cms/djangocms-versioning/commit/d8c570daa5f7805e8be51f15545fe77b24c44dafReference added —https://github.com/django-cms/djangocms-versioning/pull/573Reference added —https://github.com/django-cms/djangocms-versioning/releases/tag/2.6.1Reference added —https://github.com/django-cms/djangocms-versioning/security/advisories/GHSA-5g9x-qwh5-33x4Source identifier: security-advisories@github.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-69138"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-69138.svg?lang=en" alt="CVE-2026-69138 – NEOSEC Intel" height="20"></a>