Translate WordPress with GTranslate <= 2.8.10 - Open Redirect

2017-02-03 00:00

Strategic Overview

Status: Patched in 2.8.11
Affected Plugin: Translate WordPress with GTranslate
Affected Version: < 2.8.11
CVSS: 6.1Medium
Weakness type: CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE: CVE pending

View all Translate WordPress with GTranslate vulnerabilities

At a glance

This record tracks a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Translate WordPress with GTranslate WordPress plugin, affecting versions < 2.8.11. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.11; sites on affected versions should update now. Disclosed February 2017.

Vulnerability Overview

The Google Translate Plugin for WordPress is vulnerable to Open Redirect in versions up to, and including, 2.8.10. This is due to the application failing to properly verify user-supplied input from the `gurl` parameter. This makes it possible for unauthenticated attackers to exploit this issue and redirect users to arbitrary web sites and conduct phishing attacks; other attacks are also possible.

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.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in Translate WordPress with GTranslate < 2.8.11 takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For Translate WordPress with GTranslate the fix is 2.8.11: builds < 2.8.11 are affected, anything from 2.8.11 onward is not.

Remediation

Update to version 2.8.11, or a newer patched version

How does WordSec protect against this?

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

Firewall
Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/b980b8e2-73e6-4afc-a24c-c7c98283e85b

Related records

Other vulnerabilities in Translate WordPress with GTranslate

CVSS Vector

6.1

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/