{"answers":{"affected":"3 open source packages ship an affected version, including django-cms.","exploited":"There is no known exploitation of CVE-2026-54624 in the wild and no public exploit code.","fix":"Upgrade django-cms to 5.0.8 or later.","what":"CVE-2026-54624 is a medium-severity missing authorization vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54624 and fix it if it is affected.\n\nWhat it is: CVE-2026-54624 is a medium-severity missing authorization vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54624 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-54624/ (Markdown: https://insights.sbomify.com/CVE-2026-54624/index.md)","id":"CVE-2026-54624","markdown":"https://insights.sbomify.com/CVE-2026-54624/index.md","name":"CVE-2026-54624","record":{"aliases":["GHSA-vgxm-h9gx-h9w7","PYSEC-2026-3826"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"django CMS","requires_auth":"low_privilege","summary":"Staff users can bypass page-view permissions to read restricted page structure details in django CMS when specific permission settings are enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.8, render_object_structure in cms/views.py renders cms/toolbar/structure.html for a PageContent object without calling user_can_view_page(). Any staff account can request a restricted page’s structure when CMS_PERMISSION is enabled and the page has view restrictions or CMS_PUBLIC_FOR is set to staff. The response exposes plugin get_short_description() values, including link names, URLs, and text snippets, rather than only the page shape. This issue is fixed in versions 5.0.8.","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: Structure endpoint bypasses page-view permission","id":"CVE-2026-54624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"django CMS: Page cache ignores plugin-declared Vary headers (disclosure \u0026 poisoning)","id":"CVE-2026-54625"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-vgxm-h9gx-h9w7"},{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-vgxm-h9gx-h9w7"},{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"PYSEC-2026-3826"}],"prev":{"headline":"django CMS: Plugin move endpoint allows cyclic reparenting (DoS)","id":"CVE-2026-54623"},"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":"Staff users can bypass page-view permissions to read restricted page structure details in django CMS when specific permission settings are enabled.","url":"https://insights.sbomify.com/CVE-2026-54624/"}