CVE-2016-10882

Google Doc Embedder <= 2.6.1 - Cross-Site Request Forgery

2016-09-27 00:00
Tristan Madani

Strategic Overview

Status
Patched in 2.6.2
Affected Plugin
Google Doc Embedder
Affected Version
<= 2.6.1
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2016-10882
View all Google Doc Embedder vulnerabilities

At a glance

CVE-2016-10882 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Google Doc Embedder WordPress plugin, affecting versions <= 2.6.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.6.2; sites on affected versions should update now. Disclosed September 2016, reported by Tristan Madani.

Vulnerability Overview

The Google Doc Embedder plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.6.1. This makes it possible for unauthenticated attackers to conduct attacks such as cross-site scripting via 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)

Reaching this weakness in Google Doc Embedder <= 2.6.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 Google Doc Embedder the fix is 2.6.2: builds <= 2.6.1 are affected, anything from 2.6.2 onward is not.

Remediation

Update to version 2.6.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2016-10882https://www.wordfence.com/threat-intel/vulnerabilities/id/5aaf9bb4-bafe-415f-923d-041ef80cabachttps://nvd.nist.gov/vuln/detail/CVE-2016-10882

Related records

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