CVE-2026-71239
Authenticated Django template injection in DjangoCRM massmail exposing data and CSRF tokens
Is CVE-2026-71239 being exploited?
Not confirmed. CVE-2026-71239 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-71239?
CVE-2026-71239 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71239?
Not known from our data. No patch reference has been recorded for CVE-2026-71239, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71239 affect?
CVE-2026-71239 affects DjangoCRM (massmail module), Django apps using Template() with user-controlled input. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71239?
Restrict mass-mail edit rights, remove/sanitize template syntax in messages, audit mails, apply vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated template injection allowing disclosure of user data and password hashes, CSRF token theft, and inclusion of arbitrary registered templates.
Immediate action required