{"answers":{"affected":"3 open source packages ship an affected version, including django-cms.","exploited":"There is no known exploitation of CVE-2026-75526 in the wild and no public exploit code.","fix":"Upgrade django-cms to 5.0.9 or later.","what":"CVE-2026-75526 is a medium-severity cross-site scripting vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-75526 and fix it if it is affected.\n\nWhat it is: CVE-2026-75526 is a medium-severity cross-site scripting vulnerability in django-cms, published on 20 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-75526 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-cms (PyPI): affected from 5.0.8; fixed in 5.0.9\n- django-cms (PyPI): affected from 5.0.8; fixed in 5.0.9\n- django-cms (PyPI): affected from 5.0.8; 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-75526/ (Markdown: https://insights.sbomify.com/CVE-2026-75526/index.md)","id":"CVE-2026-75526","markdown":"https://insights.sbomify.com/CVE-2026-75526/index.md","name":"CVE-2026-75526","record":{"aliases":["GHSA-hvq6-2r72-p2x7","PYSEC-2026-3825"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"django CMS","requires_auth":"low_privilege","summary":"Stored XSS in django CMS edit mode allows attackers to execute arbitrary scripts in an editor's browser via unescaped exception messages.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. From 5.0.8 until 5.0.9, ContentRenderer.render_placeholder in cms/plugin_rendering.py can pass stored, attacker-controlled values to ContentRenderer.render_exception when plugin rendering fails in edit mode. Values from get_short_description(), the exception message, the placeholder, or placeholder.source are interpolated into a cms-rendering-exception heading and later returned through mark_safe. Because the heading is not escaped, stored HTML executes in an editor’s browser, and settings.DEBUG does not prevent the custom heading from rendering. The fix uses format_html to escape the message before safe placeholder output is returned. 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: Stored XSS in edit-mode plugin exception rendering","id":"CVE-2026-75526","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Broken Link Checker \u003c= 2.4.13 - Unauthenticated Stored Cross-Site Scripting via Comment Author URL / Link Log","id":"CVE-2026-75528"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["5.0.8"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-hvq6-2r72-p2x7"},{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["5.0.8"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-hvq6-2r72-p2x7"},{"ecosystem":"PyPI","fixed":["5.0.9"],"introduced":["5.0.8"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"PYSEC-2026-3825"}],"prev":{"headline":"OpenReception: unauthenticated ML-KEM key injection into the staff-crypto recipient directory in any tenant","id":"CVE-2026-75525"},"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":"Stored XSS in django CMS edit mode allows attackers to execute arbitrary scripts in an editor's browser via unescaped exception messages.","url":"https://insights.sbomify.com/CVE-2026-75526/"}