GHSA-fwjf-m4qw-9f2x: django-cms (CVE-2026-54625)

Package	Ecosystem	Affected	Fixed in
django-cms	PyPI	<5.0.8	5.0.8

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

django-cms versions before 5.0.8 cache anonymous pages without including the request headers that plugins declare through get_vary_cache_on(). An unauthenticated attacker can prime the cache with content rendered from chosen header values, and other visitors may then receive that variant, leading to information disclosure and cache poisoning. This applies only when CMS_PAGE_CACHE is enabled and at least one plugin implements get_vary_cache_on(). Upgrade to django-cms 5.0.8. Until then, disable CMS_PAGE_CACHE or avoid plugins that use get_vary_cache_on().

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
4.8	Medium	3.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N	CNA (GitHub_M)

CISA KEV Not listed.
EPSS 0.0018, the 7th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

31 Oct 2026, 14:10 UTC First seen by agentprime
31 Oct 2026, 14:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.