# CVE-2026-63003: django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction bypass)

> Attackers can bypass access controls to read content from unauthorized pages via the page duplication feature in django CMS.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-6x92-6vx4-5fwr, PYSEC-2026-3821

## What is CVE-2026-63003?

CVE-2026-63003 is a medium-severity missing authorization vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-63003?

3 open source packages ship an affected version, including django-cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django-cms` | PyPI | All versions | 5.0.9 |
| `django-cms` | PyPI | All versions | 5.0.9 |
| `django-cms` | PyPI | All versions | 5.0.9 |

## How do I fix CVE-2026-63003?

Upgrade django-cms to 5.0.9 or later.

## Is CVE-2026-63003 being exploited?

There is no known exploitation of CVE-2026-63003 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63003 and fix it if it is affected.

What it is: CVE-2026-63003 is a medium-severity missing authorization vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63003 in the wild and no public exploit code.

Affected packages and fixed versions:
- django-cms (PyPI): affected all versions; fixed in 5.0.9
- django-cms (PyPI): affected all versions; fixed in 5.0.9
- django-cms (PyPI): affected all versions; fixed in 5.0.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63003/ (Markdown: https://insights.sbomify.com/CVE-2026-63003/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63003
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63003
- OSV: https://osv.dev/vulnerability/CVE-2026-63003

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63003/
Summaries are generated and may contain mistakes; the official description above is the record.