CVE-2017-6591: There is a cross-site scripting vulnerability in django-epiceditor 0.2.3 via crafted content in a form field.
CVE-2017-6591 is a medium-severity flaw (CVSS 6.1) affecting django-epiceditor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
There is a cross-site scripting vulnerability in django-epiceditor 0.2.3 via crafted content in a form field.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.8% (top 42%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2017-03-09 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-6591?
django-epiceditor: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2017-6591 being exploited?
CVE-2017-6591 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-6591 affect?
CVE-2017-6591 affects django-epiceditor. Severity is medium (CVSS 6.1). There is a cross-site scripting vulnerability in django-epiceditor 0.2.3 via crafted content in a form field.
How urgent is CVE-2017-6591?
Priority 41/100. Public exploit reference