Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

safe editor vulnerabilities and fixes

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

Also searched as: safeeditor.

safe editor has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-09-17. Highest priority: CVE-2016-10976 (score 45/100).

FAQ

How do I fix safe editor 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 safe editor being exploited right now?

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

Which safe editor CVE should I patch first?

CVE-2016-10976 currently ranks highest (45/100): The safe-editor plugin before 1.2 for WordPress has no se_save authentication, with resultant XSS..

← Back to latest CVEs