{"answers":{"affected":"3 open source packages ship an affected version, including django-cms.","exploited":"There is no known exploitation of CVE-2026-54623 in the wild and no public exploit code.","fix":"Upgrade django-cms to 5.0.8 or later.","what":"CVE-2026-54623 is a high-severity denial of service 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-54623 and fix it if it is affected.\n\nWhat it is: CVE-2026-54623 is a high-severity denial of service 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-54623 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-54623/ (Markdown: https://insights.sbomify.com/CVE-2026-54623/index.md)","id":"CVE-2026-54623","markdown":"https://insights.sbomify.com/CVE-2026-54623/index.md","name":"CVE-2026-54623","record":{"aliases":["GHSA-8jj7-4v57-frf5","PYSEC-2026-3822"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"django CMS","requires_auth":"low_privilege","summary":"A staff user can create cyclic plugin relationships in django CMS, causing infinite recursion and denial of service during rendering or tree operations.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"},{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.8, the move_plugin endpoint in cms/admin/placeholderadmin.py accepts an attacker-controlled plugin_parent value without rejecting a plugin’s own identifier or a descendant identifier. A staff user with plugin-change permission under CMS_PERMISSION can create a parent_id cycle in the plugin tree. The _get_descendants_cte and _get_ancestors_cte queries in cms/models/pluginmodel.py have no cycle guard, so get_descendants() and later rendering, copy, or delete operations can recurse indefinitely or reach a database recursion limit, corrupting the tree and consuming request workers. 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: Plugin move endpoint allows cyclic reparenting (DoS)","id":"CVE-2026-54623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"django CMS: Structure endpoint bypasses page-view permission","id":"CVE-2026-54624"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-8jj7-4v57-frf5"},{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-8jj7-4v57-frf5"},{"ecosystem":"PyPI","fixed":["5.0.8"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"PYSEC-2026-3822"}],"prev":{"headline":"django CMS: Clipboard copy IDOR discloses unauthorized plugin content","id":"CVE-2026-54622"},"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":"A staff user can create cyclic plugin relationships in django CMS, causing infinite recursion and denial of service during rendering or tree operations.","url":"https://insights.sbomify.com/CVE-2026-54623/"}