Django Crm
Approved changes feed: RSS · Atom
cpe:2.3:a:djangocrm:django-crm:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Djangocrm (d964e018-83d0-50ed-9f3a-a4475f7eef5f) |
|---|---|
| Product | Django Crm (66d4b22b-5ef7-5526-891e-64445f17294e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-90806 |
vulnerable | 2026-09-16 04:33:05.434443 |
DjangoCRM django-crm Bulk Case Update bulk_views.py BulkUpdateCasesView authorization
MEDIUM (6.3)
A vulnerability has been found in DjangoCRM django-crm up to 1.2. This vulnerability affects the function BulkUpdateCasesView of the file backend/cases/bulk_views.py of the component Bulk Case Update. The manipulation leads to missing authorization. The attack is possible to be carried out remotely. Upgrading to version 1.3.0 is able to resolve this issue. The identifier of the patch is 799bb1210238f402c0c4948c8eedb6e61cd0c8d7. You should upgrade the affected component.
Published: 2026-09-14T17:30:08.547Z
Updated: 2026-09-14T17:57:14.310Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-71239 |
vulnerable | 2026-09-16 04:32:59.744577 |
DjangoCRM - Server-Side Template Injection in Mass Mail Message Rendering
HIGH (8.1)
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.
Published: 2026-08-05T10:56:36.819Z
Updated: 2026-08-10T11:45:44.417Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-71238 |
vulnerable | 2026-09-16 04:32:59.674755 |
DjangoCRM - Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery
CRITICAL (9.1)
DjangoCRM ships with its Django SECRET_KEY hardcoded directly in the committed webcrm/settings.py rather than read from an environment variable. Since this key is used for session signing, CSRF token generation, and password reset tokens, anyone who reads the public repository can forge valid session cookies (including for the superadmin account), forge CSRF tokens, and forge password reset tokens, achieving full account takeover.
Published: 2026-08-05T10:56:33.934Z
Updated: 2026-08-10T11:45:42.375Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-71240 |
vulnerable | 2026-09-16 04:32:59.407860 |
DjangoCRM - Unauthenticated Open Redirect via toggle_default_sorting next_url Parameter
MEDIUM (4.3)
DjangoCRM's toggle_default_sorting view is the only route in common/urls.py that is not wrapped in login_required or staff_member_required, and it redirects to a caller-supplied next_url GET parameter after only checking secure_url(next_url), which merely verifies the target host matches the current site's domain (blocking only cross-domain redirects) while allowing any same-site path with no authentication required to reach the view.
Published: 2026-08-05T10:56:39.721Z
Updated: 2026-08-10T11:45:46.461Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.