{"answers":{"affected":"3 open source packages ship an affected version, including django-epiceditor. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-6591 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-6591 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2017-6591 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2017-6591 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-epiceditor (PyPI): affected all versions; no fix listed\n- django-epiceditor (PyPI): affected all versions; no fix listed\n- django-epiceditor (PyPI): affected all versions; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-6591/ (Markdown: https://insights.sbomify.com/CVE-2017-6591/index.md)","id":"CVE-2017-6591","markdown":"https://insights.sbomify.com/CVE-2017-6591/index.md","name":"CVE-2017-6591","record":{"aliases":["GHSA-xp5m-4c9f-498q","PYSEC-2017-86"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Django editor plugin","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in user browsers via crafted content in django-epiceditor form fields.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django-epiceditor","vendor":"django-epiceditor_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"There is a cross-site scripting vulnerability in django-epiceditor 0.2.3 via crafted content in a form field.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"django-epiceditor vulnerable to XSS in form field","id":"CVE-2017-6591","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2017"},"n_packages":3,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2017-6594"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"django-epiceditor","purl":null,"source":"GHSA-xp5m-4c9f-498q"},{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"django-epiceditor","purl":"pkg:pypi/django-epiceditor","source":"GHSA-xp5m-4c9f-498q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":[],"package":"django-epiceditor","purl":"pkg:pypi/django-epiceditor","source":"PYSEC-2017-86"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2017-6590"},"products":["n/a"],"published":"2017-03-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts in user browsers via crafted content in django-epiceditor form fields.","url":"https://insights.sbomify.com/CVE-2017-6591/"}