# CVE-2026-54622: django CMS: Clipboard copy IDOR discloses unauthorized plugin content

> Staff users can bypass authorization checks to copy and read unauthorized plugin content from other pages via the clipboard endpoint.

- **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:** 20 Aug 2026
- **Also known as:** GHSA-4xfr-4p46-gc6p, PYSEC-2026-3820

## What is CVE-2026-54622?

CVE-2026-54622 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.8, the copy_plugins endpoint in cms/admin/placeholderadmin.py authorizes only the destination clipboard. The _copy_plugin_to_clipboard and _copy_placeholder_to_clipboard paths accept source_placeholder_id and source_plugin_id values but use has_copy_plugins_permission and check_source only for the requesting user’s clipboard, without validating the source placeholder. Under CMS_PERMISSION, a staff user with the global add permission for a plugin type can copy plugins from an unauthorized page or placeholder into the user’s clipboard and read secret text, link names, and URLs. This issue is fixed in versions 5.0.8.

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

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

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


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

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

Upgrade django-cms to 5.0.8 or later.

## Is CVE-2026-54622 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54622 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-54622 in the wild and no public exploit code.

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

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-54622/ (Markdown: https://insights.sbomify.com/CVE-2026-54622/index.md)
```

## Sources

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

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