WP Editor < 1.2.6 - Incorrect Permission Assignment or Protection
Strategic Overview
- Status
- Patched in 1.2.6
- Affected Plugin
- WP Editor
- Affected Version
< 1.2.6- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2016-10886
At a glance
CVE-2016-10886 is a critical-severity Missing Authorization vulnerability in the WP Editor WordPress plugin, affecting versions < 1.2.6. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.2.6; sites on affected versions should update now. Disclosed January 2021.
Vulnerability Overview
The wp-editor plugin before 1.2.6 for WordPress has incorrect permissions.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in WP Editor < 1.2.6 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Editor the fix is 1.2.6: builds < 1.2.6 are affected, anything from 1.2.6 onward is not.
Remediation
Update to version 1.2.6, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Editor 1.2.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Editor
- 8.8CVE-2026-3772: WP Editor <= 1.2.9.2 CSRF to Remote Code Execution
CVE-2026-3772 - 8.8CVE-2016-10885: WP Editor < 1.2.6 Cross-Site Request Forgery
CVE-2016-10885 - 7.2CVE-2025-3294: WP Editor Directory Traversal to Arbitrary File Update
CVE-2025-3294 - 7.2CVE-2022-2446: WP Editor <= 1.2.9 PHAR Deserialization
CVE-2022-2446 - 7.2CVE-2021-24151: WP Editor <= 1.2.6.3 SQL injection
CVE-2021-24151 - 6.1CVE-2024-24700: WP Editor <= 1.2.8 Reflected Cross-Site Scripting
CVE-2024-24700 - 6.1CVE-2016-10877: WP Editor <= 1.2.6.2 Cross-Site Scripting
CVE-2016-10877 - 5.3CVE-2024-25591: WP Editor <= 1.2.7 Sensitive Information Exposure
CVE-2024-25591
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C