Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

epiceditor vulnerabilities and fixes

Recent CVEs affecting epiceditor, with upgrade or downgrade steps. 1 tracked.

epiceditor has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-03-09. Highest priority: CVE-2017-6589 (score 39/100).

FAQ

How do I fix epiceditor vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is epiceditor being exploited right now?

None of the tracked epiceditor CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which epiceditor CVE should I patch first?

CVE-2017-6589 currently ranks highest (39/100): EpicEditor through 0.2.3 has Cross-Site Scripting because of an insecure default marked.js configuration.

← Back to latest CVEs