CVE-2016-10946

Wp-D3 < 2.4.1 - Cross-Site Request Forgery

2016-11-21 00:00
Anonymous

Strategic Overview

Status
Patched in 2.4.1
Affected Plugin
Wp-D3
Affected Version
< 2.4.1
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2016-10946
View all Wp-D3 vulnerabilities

At a glance

CVE-2016-10946 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Wp-D3 WordPress plugin, affecting versions < 2.4.1. 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 2.4.1; sites on affected versions should update now. Disclosed November 2016.

Vulnerability Overview

The wp-d3 plugin before 2.4.1 for WordPress has CSRF.

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)

Reaching this weakness in Wp-D3 < 2.4.1 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-D3 the fix is 2.4.1: builds < 2.4.1 are affected, anything from 2.4.1 onward is not.

Remediation

Update to version 2.4.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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