CVE-2026-71239: DjangoCRM: Server-Side Template Injection in Mass Mail Message Rendering
DjangoCRM's massmail module renders user-controlled EmlMessage fields (subject, content) through Django's Template() constructor with no sanitization, in at least three locations: messagepreviews.py builds an f-string embedding message.subject/message.content directly into a Template() call; emailcreators.py passes emlmessage.subject directly as a template string to Template(); and helpers.py contains the same f-string interpolation pattern. An authenticated user with mass-mail message edit rights can inject Django template syntax ({{ }} / {% %}) that executes at render time, enabling disclosure of other users' data and password hashes via request context variables, CSRF token forgery, and inclusion of arbitrary registered templates.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-71239?
CVE-2026-71239 has a high severity rating of 8.8.
What risk does CVE-2026-71239 pose?
CVE-2026-71239 poses a risk score of 62, indicating a significant vulnerability.
How do I fix CVE-2026-71239?
To fix CVE-2026-71239, ensure that user-controlled inputs are properly sanitized before being rendered in templates.
What kind of injection vulnerability is described in CVE-2026-71239?
CVE-2026-71239 describes a Server-Side Template Injection vulnerability due to unsanitized input in DjangoCRM.
Which module of DjangoCRM is affected by CVE-2026-71239?
The massmail module of DjangoCRM is affected by CVE-2026-71239 due to its handling of EmlMessage fields.