{"answers":{"affected":"3 open source packages ship an affected version, including djangocms-attributes-field.","exploited":"There is no known exploitation of CVE-2024-11406 in the wild and no public exploit code.","fix":"Upgrade djangocms-attributes-field to 4.0.0 or later.","what":"CVE-2024-11406 is a medium-severity cross-site scripting vulnerability in django CMS Attributes Fields, published on 20 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-11406 and fix it if it is affected.\n\nWhat it is: CVE-2024-11406 is a medium-severity cross-site scripting vulnerability in django CMS Attributes Fields, published on 20 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-11406 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- djangocms-attributes-field (PyPI): affected all versions; fixed in 4.0.0\n- djangocms-attributes-field (PyPI): affected all versions; fixed in 4.0.0\n- djangocms-attributes-field (PyPI): affected all versions; fixed in 4.0.0\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-2024-11406/ (Markdown: https://insights.sbomify.com/CVE-2024-11406/index.md)","id":"CVE-2024-11406","markdown":"https://insights.sbomify.com/CVE-2024-11406/index.md","name":"CVE-2024-11406","record":{"aliases":["GHSA-vxcv-4xvf-pc22","PYSEC-2026-1303"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"django CMS plugin","requires_auth":"high_privilege","summary":"Attackers can inject malicious scripts into django CMS Attributes Fields, potentially executing code in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TR-CERT","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in django CMS Association django CMS Attributes Fields allows Stored XSS.\n\nThis issue affects django CMS Attributes Fields: before 4.0.","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":"Stored XSS in django CMS Attributes Fields","id":"CVE-2024-11406","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":3,"n_references":6,"next":{"headline":"Denial of Service through Data corruption in gRPC-C++","id":"CVE-2024-11407"},"packages":[{"ecosystem":"PyPI","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"djangocms-attributes-field","purl":null,"source":"GHSA-vxcv-4xvf-pc22"},{"ecosystem":"PyPI","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"djangocms-attributes-field","purl":"pkg:pypi/djangocms-attributes-field","source":"GHSA-vxcv-4xvf-pc22"},{"ecosystem":"PyPI","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"djangocms-attributes-field","purl":"pkg:pypi/djangocms-attributes-field","source":"PYSEC-2026-1303"}],"prev":{"headline":"WP Front-end login and register \u003c= 2.1.0 - Reflected Cross-Site Scripting","id":"CVE-2024-11405"},"products":["django CMS Attributes Fields"],"published":"2024-11-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-06-02","vendors":["django CMS Association"]},"summary":"Attackers can inject malicious scripts into django CMS Attributes Fields, potentially executing code in victim browsers.","url":"https://insights.sbomify.com/CVE-2024-11406/"}