CVE-2016-10976 json
The safe-editor plugin before 1.2 for WordPress has no se_save authentication, with resultant XSS.
published 2019-09-17 7 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1967
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The safe-editor plugin before 1.2 for WordPress has no se_save authentication, with resultant XSS.
Patch / fix
- kodebyraaet safe_editor 1.2
Exploit prediction
1.75% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Safe Editor Plugin < 1.2 - CSS/JS-injection nuclei detection template
- wpvulndb.com https://wpvulndb.com/vulnerabilities/8497 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpvulndb.com
/vulnerabilities/8497
exploit, third-party-advisory
-
wordpress.org
/plugins/safe-editor/#developers
product
Sources
- CVE List CVE-2016-10976
- NVD CVE-2016-10976
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.