cve.bz

CVE-2026-54625 django-cms django-cms

4.8 mediumEPSS 0.2%Fix available

Medium (4.8) in django-cms django-cms. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in django-cms 5.0.8.

On this page
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.

Severity

CVSS 3.1

4.8 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
CWE-524 Use of Cache Containing Sensitive Information
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • django-cms (PyPI): fixed in 5.0.8

Ask an AI about this CVE

Show the promptExplain CVE-2026-54625 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54625?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54625?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54625 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
django-cms< 5.0.8
django-cms>= 5.1.0a1, < 5.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fwjf-m4qw-9f2xPyPIdjango-cms<5.0.85.0.8
PYSEC-2026-3824PyPIdjango-cms<5.0.85.0.8

Attack patterns (CAPEC)

  • CAPEC-204 Lifting Sensitive Data Embedded in Cache Severity: Medium
  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-141 Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON