CVE-2026-63003 json
django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction bypass)
published 2mo ago modified 16d ago also EUVD-2026-63570 , GHSA-6x92-6vx4-5fwr , PYSEC-2026-3821
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.9, page duplication lacks an object-level authorization check on the source page. In cms/admin/forms.py, DuplicatePageForm.source accepts any Page, the AddPageForm constructor does not narrow a hidden source field, AddPageForm.clean does not validate the source against the user, and AddPageForm.save calls from_source. In cms/admin/pageadmin.py, duplicate and PageAdmin.has_add_permission check only whether a staff user may add a page. A crafted source value can therefore copy every placeholder and plugin from an unauthorized page with permissions=False, stripping source view restrictions and exposing content across sites or restricted subtrees when CMS_PERMISSION is enabled. This issue is fixed in versions 5.0.9.
Patch / fix
- pypi django-cms 5.0.9
- django-cms django_cms 5.0.9
Is CVE-2026-63003 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django-cms | <5.0.9 |
5.0.9 |
Affected products
- django-cms django-cms
Classification
References
-
github.com
/django-cms/django-cms/pull/8713
web
-
github.com
/django-cms/django-cms/commit/3e1ccf7573eb1a74ebbbfaaa812c1f5cadf14e6c
web
-
github.com
/django-cms/django-cms/security/advisories/GHSA-6x92-6vx4-5fwr
web
-
github.com
/django-cms/django-cms/releases/tag/5.0.9
web
-
github.com
/django-cms/django-cms
package
-
pypi.org
/project/django-cms
package
-
github.com
/advisories/GHSA-6x92-6vx4-5fwr
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-63003
advisory
Sources
- CVE List CVE-2026-63003
- GitHub Advisory GHSA-6x92-6vx4-5fwr
- NVD CVE-2026-63003
- OSV PYSEC-2026-3821
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.