dbcve.org
Google Doc EmbedderWordPress extension · Google Doc Embedder Project

CVE-2016-10881

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-14
Fix available
A fix is available. Upgrade to 2.6.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The google-document-embedder plugin before 2.6.2 for WordPress has XSS.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The google-document-embedder WordPress plugin before version 2.6.2 contains a Cross-Site Scripting (XSS) vulnerability. Attackers could inject malicious scripts through the plugin's input fields that would execute in the context of other users' browsers, potentially stealing session cookies or performing actions on behalf of authenticated users.

MitigationUpdate the google-document-embedder plugin to version 2.6.2 or later to patch the XSS vulnerability. Additionally, consider using a web application firewall (WAF) as a temporary protective measure until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Google Doc EmbedderWordPress extension
Affected:< 2.6.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Doc Embedder plugin version
    Locate the main plugin file (google-document-embedder.php) in wp-content/plugins/google-document-embedder/ and open it. Look for the 'Version:' header in the file comments, or use command: grep -i 'Version:' /path/to/wordpress/wp-content/plugins/google-document-embedder/google-document-embedder.php
    Affected if The version number displayed is lower than 2.6.2, or no version is declared in the plugin file headers
  2. Verify the plugin is active
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Confirm that Google Doc Embedder shows an 'Active' status under the plugin name
    Affected if The plugin is installed and currently activated in WordPress, and the version is below 2.6.2
  3. Check for publicly accessible input fields
    Inspect pages on the site where the Google Doc Embedder shortcode or block is used. Look for any user-accessible input forms or parameters that accept user-supplied content (such as document URLs or display options) that could be manipulated
    Affected if The plugin is active and exposes input fields or shortcode parameters that accept user-supplied data without sanitization
  4. Review plugin files for sanitization functions
    Examine the main plugin PHP file for presence of sanitization functions like esc_html(), esc_attr(), sanitize_text_field(), or wp_kses() applied to user inputs. Search for the functions that handle shortcode attributes or form submissions
    Affected if No sanitization functions are found on input handling code, or user inputs are directly output without escaping

Your site is affected if the Google Doc Embedder plugin version is below 2.6.2 and the plugin is actively installed on your WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.6.2 or later
Fixed in 2.6.2
Interim mitigation

Update the google-document-embedder plugin to version 2.6.2 or later to patch the XSS vulnerability. Additionally, consider using a web application firewall (WAF) as a temporary protective measure until the update can be applied.

Fix this in Google Doc Embedder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10881 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data