{"answers":{"affected":"3 open source packages ship an affected version, including django-cms.","exploited":"There is no known exploitation of CVE-2026-54625 in the wild and no public exploit code.","fix":"Upgrade django-cms to 5.0.8 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-54625 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-54625 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-cms (PyPI): affected all versions; fixed in 5.0.8\n- django-cms (PyPI): affected all versions; fixed in 5.0.8\n- django-cms (PyPI): affected all versions; fixed in 5.0.8\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54625/ (Markdown: https://insights.sbomify.com/CVE-2026-54625/index.md)","id":"CVE-2026-54625","markdown":"https://insights.sbomify.com/CVE-2026-54625/index.md","name":"CVE-2026-54625","record":{"aliases":["GHSA-fwjf-m4qw-9f2x","PYSEC-2026-3824"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"django CMS","requires_auth":"none","summary":"Attackers can read other users' data or poison the cache in django CMS when page caching is enabled and plugins use Vary headers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"},{"id":"CWE-349","name":"Acceptance of Extraneous Untrusted Data With Trusted Data"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"django CMS: Page cache ignores plugin-declared Vary headers (disclosure \u0026 poisoning)","id":"CVE-2026-54625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":7,"next":{"headline":"SAIL: Heap out-of-bounds write in SAIL TGA decoder (indexed-RLE bpp/stride mismatch)","id":"CVE-2026-54626"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-fwjf-m4qw-9f2x"},{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-fwjf-m4qw-9f2x"},{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"PYSEC-2026-3824"}],"prev":{"headline":"django CMS: Structure endpoint bypasses page-view permission","id":"CVE-2026-54624"},"products":["django-cms"],"published":"2026-08-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["django-cms"]},"summary":"Attackers can read other users' data or poison the cache in django CMS when page caching is enabled and plugins use Vary headers.","url":"https://insights.sbomify.com/CVE-2026-54625/"}