Vulnerabilities in pkg:pypi/django-cms

PACKAGE
Advisory Identifier: GHSA-fwjf-m4qw-9f2x
Advisory Summary

CVE-2026-54625 is a MODERATE (CVSS 4.8) page cache ignores plugin-declared vary vulnerability (CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data) affecting django CMS libraries in the PyPI ecosystem. The issue involves page cache ignores plugin-declared vary headers (disclosure & poisoning). Remediation is available by upgrading affected packages to version 5.0.8.

10 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/django-cms

10 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/django-cms. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fwjf-m4qw-9f2x CVE-2026-54625 MODERATE django CMS: Page cache ignores plugin-declared Vary headers (disclosure & poisoning)
GHSA-8jj7-4v57-frf5 CVE-2026-54623 HIGH django CMS: Plugin move endpoint allows cyclic reparenting (DoS)
GHSA-8qj2-c6q4-f399 CVE-2026-61663 MODERATE django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff
GHSA-6x92-6vx4-5fwr CVE-2026-63003 MODERATE django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction bypass)
GHSA-hvq6-2r72-p2x7 CVE-2026-75526 MODERATE django CMS: Stored XSS in edit-mode plugin exception rendering
GHSA-vgxm-h9gx-h9w7 CVE-2026-54624 MODERATE django CMS: Structure endpoint bypasses page-view permission
GHSA-4xfr-4p46-gc6p CVE-2026-54622 MODERATE django CMS: Clipboard copy IDOR discloses unauthorized plugin content
GHSA-gv5h-5655-h4mv CVE-2024-11319 MODERATE django CMS Cross-Site Scripting (XSS)
GHSA-hx7c-qpfq-xcrp CVE-2021-44649 MODERATE Cross-site Scripting in django-cms
GHSA-2pqc-gv8q-pvqv CVE-2015-5081 HIGH django-cms CSRF Vulnerability

CVE-2026-54625 at a Glance

CVE Identifier CVE-2026-54625
GHSA Identifier GHSA-fwjf-m4qw-9f2x
Severity MODERATE
CVSS v3.1 Base Score 4.8
CWE Classification CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data
Affected Product django CMS
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 4.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-54625

To remediate this vulnerability, upgrade all affected django CMS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

django-cms fixed: 5.0.8
pip install django-cms>=5.0.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show django-cms

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-54625, inspect your installed packages using pip:

pip show django-cms

Analyze the terminal output to locate any version of django CMS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.8), your application is affected.

Note: The pip show django-cms command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data, where the product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted. In django CMS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The CMS page cache key ignores the request headers that plugins declare via `get_vary_cache_on()`. The header is added to the response `Vary` header, but the CMS's own cache key does not incorporate the header values, so the first visitor's variant is served to all subsequent visitors regardless of their header values. ### Details `_page_cache_key` (in `cms/cache/page.py`) keys only on cache prefix, site, language, path and timezone. `set_page_cache` collects the plugin-declared vary headers and calls `patch_vary_headers(response, ...)` (affecting only the emitted `Vary` header), but stores and retrieves the cached page under the header-agnostic key. `get_page_cache` therefore returns whichever variant was cached first. ### Impact - **Information disclosure:** when a plugin varies its output on a request header (e.g. `Country-Code`), the variant rendered for the first anonymous visitor is served to everyone until the entry expires, leaking request-specific content across users. - **Cache poisoning:** an unauthenticated attacker can prime the anonymous page cache with content rendered from attacker-chosen header values, which is then served to subsequent visitors. Applies only when `CMS_PAGE_CACHE` is enabled and at least one plugin implements `get_vary_cache_on()`. ### Patches Fixed in 5.0.8: the page cache now folds the request's values implements `get_vary_cache_on()`. ### Patches Fixed in 5.0.8: the page cache now folds the request's values for plugin-declared vary headers into the content key. The set of vary headers is persisted on write and looked up first on read (mirroring Django's `learn_cache_key`/`get_cache_key`); a missing header-list entry degrades to a cache miss, never a wrong-variant hit. ### Workarounds Disable `CMS_PAGE_CACHE`, or avoid plugins that rely on `get_vary_cache_on()`, until upgraded. ### Credits Reported by the security team at the University of Sydney ([@reporter]).

CVE-2026-54625 Affected django CMS Versions

1 component(s)
Fixed Versions:
5.0.8
Product / Package Ecosystem Affected Versions Fixed Version
django-cms
PyPI
< 5.0.8
5.0.8

References

Frequently Asked Questions

What is CVE-2026-54625?
CVE-2026-54625 is a security vulnerability in django CMS involving Page cache ignores plugin-declared Vary headers (disclosure & poisoning) under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data.
Which django CMS versions are affected?
Affected versions include releases prior to 5.0.8 across affected packages: django-cms.
What version fixes CVE-2026-54625?
Upgrading to 5.0.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is django-cms affected?
Yes, django-cms is affected in releases prior to 5.0.8. Upgrade your dependency to 5.0.8 or later.
What is the CVSS score of CVE-2026-54625?
CVE-2026-54625 has a CVSS v3.1 base score of 4.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-54625?
CVE-2026-54625 is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data (The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.).
How can I check PyPI dependencies for CVE-2026-54625?
Run the dependency tree command: 'pip show django-cms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fwjf-m4qw-9f2x",
  "modified" : "2026-08-24T20:09:52Z",
  "published" : "2026-08-24T20:09:51Z",
  "aliases" : [ "CVE-2026-54625" ],
  "summary" : "django CMS: Page cache ignores plugin-declared Vary headers (disclosure & poisoning)",
  "details" : "### Summary\nThe CMS page cache key ignores the request headers that plugins declare via `get_vary_cache_on()`. The header is added to the response `Vary` header, but the CMS's own cache key does not incorporate the header values, so the first visitor's variant is served to all subsequent visitors regardless of their header values.\n\n### Details\n`_page_cache_key` (in `cms/cache/page.py`) keys only on cache prefix, site, language, path and timezone. `set_page_cache` collects the plugin-declared vary headers and calls `patch_vary_headers(response, ...)` (affecting only the emitted `Vary` header), but stores and retrieves the cached page under the header-agnostic key. `get_page_cache` therefore returns whichever variant was cached first.\n\n### Impact\n- **Information disclosure:** when a plugin varies its output on a request  header (e.g. `Country-Code`), the variant rendered for the first anonymous visitor is served to everyone until the entry expires, leaking request-specific content across users.\n- **Cache poisoning:** an unauthenticated attacker can prime the anonymous page cache with content rendered from attacker-chosen header values, which is then served to subsequent visitors.\n\nApplies only when `CMS_PAGE_CACHE` is enabled and at least one plugin implements `get_vary_cache_on()`.\n\n### Patches\nFixed in 5.0.8: the page cache now folds the request's values implements `get_vary_cache_on()`.\n\n### Patches\nFixed in 5.0.8: the page cache now folds the request's values for plugin-declared vary headers into the content key. The set of vary headers is persisted on write and looked up first on read (mirroring Django's  `learn_cache_key`/`get_cache_key`); a missing header-list entry degrades to a cache miss, never a wrong-variant hit.\n\n### Workarounds\nDisable `CMS_PAGE_CACHE`, or avoid plugins that rely on `get_vary_cache_on()`, until upgraded.\n\n### Credits\nReported by the security team at the University of Sydney ([@reporter]).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "django-cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.0.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/django-cms/django-cms/security/advisories/GHSA-fwjf-m4qw-9f2x"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54625"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django-cms/django-cms/pull/8646"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django-cms/django-cms/pull/8647"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django-cms/django-cms/commit/8758714b865ffa79c6bcd0e5c503958ea48885aa"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django-cms/django-cms/commit/d5dc1efa18d157445491c4b12c2dd1efd56f439f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/django-cms/django-cms"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django-cms/django-cms/releases/tag/5.0.8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django-cms/django-cms/releases/tag/5.1.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-349", "CWE-524" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-24T20:09:51Z",
    "nvd_published_at" : "2026-08-20T18:16:28Z"
  }
}