# CVE-2026-54625: django CMS: Page cache ignores plugin-declared Vary headers (disclosure & poisoning)

> Attackers can read other users' data or poison the cache in django CMS when page caching is enabled and plugins use Vary headers.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-fwjf-m4qw-9f2x, PYSEC-2026-3824

## What is CVE-2026-54625?

CVE-2026-54625 is a medium-severity vulnerability in django-cms, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

django CMS is a content management system powered by Django. Prior to 5.0.8 and in 5.1.0a1, the django CMS page cache in cms/cache/page.py ignores request headers declared by plugins through get_vary_cache_on(). The _page_cache_key function includes the cache prefix, site, language, path, and timezone but not the declared header values. Although set_page_cache adds those names to the response Vary header, get_page_cache retrieves the first stored variant under the same header-agnostic key. When CMS_PAGE_CACHE is enabled and a plugin varies content on a header such as Country-Code, one visitor can receive another visitor’s request-specific content, and an unauthenticated attacker can prime the cache with attacker-chosen content. This issue is fixed in versions 5.0.8 and 5.1.0.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information), CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data)

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

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-54625?

Upgrade django-cms to 5.0.8 or later.

## Is CVE-2026-54625 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54625 is a medium-severity vulnerability in django-cms, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54625 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-54625/ (Markdown: https://insights.sbomify.com/CVE-2026-54625/index.md)
```

## Sources

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

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