{"answers":{"affected":"3 open source packages ship an affected version, including django-cms.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61663 exists.","fix":"Upgrade django-cms to 5.0.9 or later.","what":"CVE-2026-61663 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-61663 and fix it if it is affected.\n\nWhat it is: CVE-2026-61663 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61663 exists.\n\nAffected packages and fixed versions:\n- django-cms (PyPI): affected all versions; fixed in 5.0.9\n- django-cms (PyPI): affected all versions; fixed in 5.0.9\n- django-cms (PyPI): affected all versions; fixed in 5.0.9\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-61663/ (Markdown: https://insights.sbomify.com/CVE-2026-61663/index.md)","id":"CVE-2026-61663","markdown":"https://insights.sbomify.com/CVE-2026-61663/index.md","name":"CVE-2026-61663","record":{"aliases":["GHSA-8qj2-c6q4-f399","PYSEC-2026-3823"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"django CMS","requires_auth":"low_privilege","summary":"Low-privileged staff users can access placeholder structure data for non-PageContent objects without proper authorization, leading to information disclosure.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.9, render_object_structure fails to authorize non-PageContent objects that use PlaceholderRelationField. An active staff user without cms.use_structure or model-level view or change permission can request the //admin/cms/placeholder/object/\u003ccontent_type_id\u003e/structure/\u003cobject_id\u003e/ endpoint with guessed content_type_id and object_id values. The response discloses placeholder slot names, plugin trees, plugin identifiers, labels, and object existence for frontend-editable objects. The fix applies user_can_view_placeholder_source to the non-PageContent branch while keeping the structure board read-only for view-only users. This issue is fixed in versions 5.0.9.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-privileged staff","id":"CVE-2026-61663","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":"websocket-driver: Denial of service via malformed Host header","id":"CVE-2026-61666"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-8qj2-c6q4-f399"},{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-8qj2-c6q4-f399"},{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"PYSEC-2026-3823"}],"prev":{"headline":"Lightdash: Unauthenticated dbt Cloud webhook with path injection leaks API key","id":"CVE-2026-61654"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-25","vendors":["django-cms"]},"summary":"Low-privileged staff users can access placeholder structure data for non-PageContent objects without proper authorization, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2026-61663/"}