PatchTheCVECVE-2016-10976: The safe-editor plugin before 1.2 for WordPress has no se_save authentication, with resultant XSS.
CVE-2016-10976 is a medium-severity flaw (CVSS 6.1) affecting safe editor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The safe-editor plugin before 1.2 for WordPress has no se_save authentication, with resultant XSS.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 1.5% (top 26%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2019-09-17 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- Nuclei scan template: Safe Editor Plugin < 1.2 - CSS/JS-injection
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2016-10976?
safe editor: upgrade to 1.2. Exact commands for each OS are on this page.
Is CVE-2016-10976 being exploited?
CVE-2016-10976 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2016-10976 affect?
CVE-2016-10976 affects safe editor. Severity is medium (CVSS 6.1). The safe-editor plugin before 1.2 for WordPress has no se_save authentication, with resultant XSS.
How urgent is CVE-2016-10976?
Priority 45/100. Public exploit reference