DjangoCRM django-crm up to 1.2 Bulk Case Update bulk_views.py BulkUpdateCasesView authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 1.16- |
Summary
A vulnerability labeled as critical has been found in DjangoCRM django-crm up to 1.2. This issue affects the function BulkUpdateCasesView of the file backend/cases/bulk_views.py of the component Bulk Case Update. The manipulation results in authorization.
This vulnerability was named CVE-2026-90806. The attack may be performed from remote. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in DjangoCRM django-crm up to 1.2. Affected is the function BulkUpdateCasesView of the file backend/cases/bulk_views.py of the component Bulk Case Update. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-90806. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 09/13/2026).
Upgrading to version 1.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 799bb1210238f402c0c4948c8eedb6e61cd0c8d7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: django-crm 1.3.0
Patch: 799bb1210238f402c0c4948c8eedb6e61cd0c8d7
Timeline
09/13/2026 Advisory disclosed09/13/2026 VulDB entry created
09/13/2026 VulDB entry last update
Sources
Advisory: 745Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-90806 (🔒)
GCVE (CVE): GCVE-0-2026-90806
GCVE (VulDB): GCVE-100-403308
Entry
Created: 09/13/2026 17:50Changes: 09/13/2026 17:50 (61)
Complete: 🔍
Submitter: Customer
Cache ID: 216::103
Submit
Accepted
- Submit #920489: Django-CRM master Missing Authorization (by Customer)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.