CVE-2016-10885

WP Editor < 1.2.6 - Cross-Site Request Forgery

2016-05-13 00:00
Anonymous

Strategic Overview

Status
Patched in 1.2.6
Affected Plugin
WP Editor
Affected Version
< 1.2.6
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2016-10885
View all WP Editor vulnerabilities

At a glance

CVE-2016-10885 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Editor WordPress plugin, affecting versions < 1.2.6. It carries a CVSS score of 8.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 May 2016.

Vulnerability Overview

The WP Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 1.2.6. This is due to missing or incorrect nonce validation on the save_settings() function, in addition to a few other functions. This makes it possible for unauthenticated attackers to modify the plugin's settings and upload files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

WP Editor < 1.2.6 carries this weakness at save_settings(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. 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?

The attempt arrives as an ordinary request to WP Editor: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Editor 1.2.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2016-10885https://www.wordfence.com/threat-intel/vulnerabilities/id/aee4fb6f-8ee6-4d6e-8167-876c9453f78fhttps://nvd.nist.gov/vuln/detail/CVE-2016-10885

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C