CVE-2019-11457 json
Cross-Site Request Forgery in MicroPyramid Django CRM
published 2019-08-27 7 y ago modified 2026-06-17 4 mo ago also GHSA-pg2f-r7pc-6fxx , PYSEC-2019-174 , EUVD-2019-0031
- cvss
- 8.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
Multiple CSRF issues exist in MicroPyramid Django CRM 0.2.1 via /change-password-by-admin/, /api/settings/add/, /cases/create/, /change-password-by-admin/, /comment/add/, /documents/1/view/, /documents/create/, /opportunities/create/, and /login/.
Exploit prediction
1.16% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.8 | CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R |
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django-crm | <=0.2.1 >=0.2.1 |
no fix listed |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
netsparker.com
/blog/web-security/
third-party-advisory, article
-
packetstormsecurity.com
/files/154219/Django-CRM-0.2.1-Cross-Site-Request-Forgery.html
web, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2019/Aug/30
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-11457
advisory
-
github.com
/MicroPyramid/Django-CRM
package
-
github.com
/advisories/GHSA-pg2f-r7pc-6fxx
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/django-crm/PYSEC-2019-174.yaml
web
-
netsparker.com
/blog/web-security
web
Sources
- CVE List CVE-2019-11457
- GitHub Advisory GHSA-pg2f-r7pc-6fxx
- NVD CVE-2019-11457
- OSV PYSEC-2019-174
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.