Google Language TranslatorWordPress extension · Gtranslate
CVE-2016-10870
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 · uneditedThe google-language-translator plugin before 5.0.06 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 · high confidenceCross-Site Scripting (XSS) vulnerability in the google-language-translator WordPress plugin affecting versions prior to 5.0.06. The vulnerability allows attackers to inject malicious scripts through plugin parameters, likely due to insufficient input sanitization and output encoding.
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 Language TranslatorWordPress extension
< 5.0.06CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the google-language-translator plugin is installedLog in to the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'google-language-translator' or 'GTranslate Google Language Translator' in the list of installed plugins.Affected if The plugin appears in the installed plugins list.
-
Identify the installed version of the pluginIn the Plugins list in WordPress admin, click on the plugin name to view details, or check the plugin's main PHP file for the 'Version' header in the plugin comment block. The version number will be displayed there.Affected if A version number is found that is lower than 5.0.06.
-
Compare the version against the affected rangeTake the version number found in the previous step and compare it to 5.0.06. Any version below 5.0.06 (such as 5.0.05, 5.0.04, 5.0.03, etc.) is affected by this vulnerability.Affected if The installed version is less than 5.0.06.
-
Verify if the plugin is currently activeIn the WordPress admin under Plugins > Installed Plugins, check the status indicator for google-language-translator. An 'Active' status means the plugin is running and the vulnerability is exploitable.Affected if The plugin is active and the version is below 5.0.06.
If the google-language-translator plugin is installed with a version lower than 5.0.06 and is currently active, the environment is affected by CVE-2016-10870.
Generated from the published advisory. Verify against your own configuration.
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 data5.0.06
Update the google-language-translator plugin to version 5.0.06 or later. If immediate update is not possible, consider temporarily disabling the plugin until the patch can be applied.
Fix this in Google Language Translator
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10870 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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