{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-71239 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71239 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71239 is a high-severity code injection vulnerability in DjangoCRM django-crm, published on 5 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-71239 and fix it if it is affected.\n\nWhat it is: CVE-2026-71239 is a high-severity code injection vulnerability in DjangoCRM django-crm, published on 5 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-71239 in the wild and no public exploit code.\n\nAffected product: DjangoCRM django-crm. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-71239/ (Markdown: https://insights.sbomify.com/CVE-2026-71239/index.md)","id":"CVE-2026-71239","markdown":"https://insights.sbomify.com/CVE-2026-71239/index.md","name":"CVE-2026-71239","record":{"aliases":["GHSA-qwf5-72hq-pg7x"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"DjangoCRM","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code via unsanitized user input in DjangoCRM's mass mail template rendering.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TuranSec","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"DjangoCRM's massmail module renders user-controlled EmlMessage fields (subject, content) through Django's Template constructor with no sanitization, in at least three locations: message_previews.py builds an f-string embedding message.subject/message.content directly into a Template call; email_creators.py passes eml_message.subject directly as a template string to Template; and helpers.py contains the same f-string interpolation pattern.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"DjangoCRM - Server-Side Template Injection in Mass Mail Message Rendering","id":"CVE-2026-71239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"DjangoCRM - Unauthenticated Open Redirect via toggle_default_sorting next_url Parameter","id":"CVE-2026-71240"},"packages":[],"prev":{"headline":"DjangoCRM - Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery","id":"CVE-2026-71238"},"products":["django-crm"],"published":"2026-08-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["DjangoCRM"]},"summary":"Attackers can execute arbitrary code via unsanitized user input in DjangoCRM's mass mail template rendering.","url":"https://insights.sbomify.com/CVE-2026-71239/"}