PatchTheCVEdjango crm vulnerabilities and fixes
Recent CVEs affecting django crm, with upgrade or downgrade steps. 2 tracked.
Also searched as: djangocrm.
django crm has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-08-27. Highest priority: CVE-2019-11457 (score 48/100).
- CVE-2019-11457 HIGH 8.8 DOWNGRADE Multiple CSRF issues exist in MicroPyramid Django CRM 0.2.1 via /change-password-by-admin/, /api/settings/add/
- CVE-2018-16552 HIGH 8.8 DOWNGRADE MicroPyramid Django-CRM 0.2 allows CSRF for /users/create/, /users/##/edit/, and /accounts/##/delete/ URIs.
FAQ
How do I fix django crm vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is django crm being exploited right now?
None of the tracked django crm CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which django crm CVE should I patch first?
CVE-2019-11457 currently ranks highest (48/100): Multiple CSRF issues exist in MicroPyramid Django CRM 0.2.1 via /change-password-by-admin/, /api/settings/add/.