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.
CVE-2026-90806
Score 6.3 from GitHub Security Advisory published 2026-09-14. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
September 14, 2026
Last Modified
September 14, 2026
Advisory Details (4)
Auto-updated Sep 14, 2026v1.3.0
Patch available: Django-CRM/Django-CRM v1.3.0
https://github.com/Django-CRM/Django-CRM/releases/tag/v1.3.0commit 799bb1210238 (Django-CRM/Django-CRM)
Patch available: Django-CRM/Django-CRM v1.3.0 (contains commit 799bb1210238)
https://github.com/Django-CRM/Django-CRM/commit/799bb1210238f402c0c4948c8eedb6e61cd0c8d7feat(tickets): implement bulk update and delete actions for tickets
Patch available: Django-CRM/Django-CRM v1.3.0 (PR #746 merged 2026-08-12)
https://github.com/Django-CRM/Django-CRM/pull/746BulkUpdateCasesView Horizontal Privilege Escalation: Any Organization Member Can Modify Arbitrary Cases, Self-Assign, and Bypass Approval in Django-CRM · Issue #745 · Django-CRM/Django-CRM · GitHub
https://github.com/Django-CRM/Django-CRM/issues/745Vendor Advisories for CVE-2026-90806(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 08:57 UTCEG score recompute
- 2026-09-20 08:57 UTCGHSA enrichment
- 2026-09-19 06:34 UTCEG score recompute
- 2026-09-19 06:34 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 04:11 UTCEG score recompute
- 2026-09-18 04:11 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 01:48 UTCEG score recompute
- 2026-09-17 01:48 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 23:25 UTCGHSA enrichment
- 2026-09-14 21:02 UTCEG score recompute
- 2026-09-14 21:02 UTCGHSA enrichment
- 2026-09-14 18:31 UTCEG score recompute
- 2026-09-14 18:05 UTCEG score recompute
- 2026-09-14 17:35 UTCEG score recompute
- 2026-09-14 17:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-90806?
When was CVE-2026-90806 disclosed?
Is CVE-2026-90806 actively exploited?
What is the CVSS score of CVE-2026-90806?
How do I remediate CVE-2026-90806?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90806
Is Your Infrastructure Affected by CVE-2026-90806?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.