# CVE-2017-6591: django-epiceditor vulnerable to XSS in form field

> Attackers can execute arbitrary scripts in user browsers via crafted content in django-epiceditor form fields.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xp5m-4c9f-498q, PYSEC-2017-86

## What is CVE-2017-6591?

CVE-2017-6591 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

There is a cross-site scripting vulnerability in django-epiceditor 0.2.3 via crafted content in a form field.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2017-6591?

3 open source packages ship an affected version, including django-epiceditor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `django-epiceditor` | PyPI | All versions | None |
| `django-epiceditor` | PyPI | All versions | None |
| `django-epiceditor` | PyPI | All versions | None |

Products: Django-Epiceditor Project Django-Epiceditor.

## How do I fix CVE-2017-6591?

No fix has been published for CVE-2017-6591 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6591 being exploited?

There is no known exploitation of CVE-2017-6591 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6591 and fix it if it is affected.

What it is: CVE-2017-6591 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6591 in the wild and no public exploit code.

Affected packages and fixed versions:
- django-epiceditor (PyPI): affected all versions; no fix listed
- django-epiceditor (PyPI): affected all versions; no fix listed
- django-epiceditor (PyPI): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6591/ (Markdown: https://insights.sbomify.com/CVE-2017-6591/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6591
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6591
- OSV: https://osv.dev/vulnerability/CVE-2017-6591

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6591/
Summaries are generated and may contain mistakes; the official description above is the record.