{"answers":{"affected":"3 open source packages ship an affected version, including django-cms.","exploited":"There is no known exploitation of CVE-2026-63003 in the wild and no public exploit code.","fix":"Upgrade django-cms to 5.0.9 or later.","what":"CVE-2026-63003 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-63003 and fix it if it is affected.\n\nWhat it is: CVE-2026-63003 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-63003 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.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-63003/ (Markdown: https://insights.sbomify.com/CVE-2026-63003/index.md)","id":"CVE-2026-63003","markdown":"https://insights.sbomify.com/CVE-2026-63003/index.md","name":"CVE-2026-63003","record":{"aliases":["GHSA-6x92-6vx4-5fwr","PYSEC-2026-3821"],"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":"Attackers can bypass access controls to read content from unauthorized pages via the page duplication feature in django CMS.","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-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, page duplication lacks an object-level authorization check on the source page. In cms/admin/forms.py, DuplicatePageForm.source accepts any Page, the AddPageForm constructor does not narrow a hidden source field, AddPageForm.clean does not validate the source against the user, and AddPageForm.save calls from_source. In cms/admin/pageadmin.py, duplicate and PageAdmin.has_add_permission check only whether a staff user may add a page. A crafted source value can therefore copy every placeholder and plugin from an unauthorized page with permissions=False, stripping source view restrictions and exposing content across sites or restricted subtrees when CMS_PERMISSION is enabled. 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":"none_known"},"has_fix":true,"headline":"django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction bypass)","id":"CVE-2026-63003","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":"Unleash: Addon webhook URL is dialed server-side with no internal-address filtering, enabling SSRF to internal services / cloud metadata and exfiltration of configured request headers","id":"CVE-2026-63004"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-6x92-6vx4-5fwr"},{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-6x92-6vx4-5fwr"},{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"PYSEC-2026-3821"}],"prev":{"headline":"REDAXO: Stored XSS in Mediapool Sync Page via Unescaped Filesystem Filenames","id":"CVE-2026-63002"},"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-21","vendors":["django-cms"]},"summary":"Attackers can bypass access controls to read content from unauthorized pages via the page duplication feature in django CMS.","url":"https://insights.sbomify.com/CVE-2026-63003/"}