CVE-2022-0770

Translate WordPress with GTranslate <= 2.9.8 & Translate WordPress – Google Language Translator <= 6.0.13 - Missing Authorization to Sensitive Information Disclosure

2022-03-07 00:00
Diogo Real

Strategic Overview

Status
Patched in 2.9.9
Affected Version
< 2.9.9
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-0770
View all Translate WordPress with GTranslate vulnerabilities

At a glance

CVE-2022-0770 is a high-severity Missing Authorization vulnerability in the Translate WordPress with GTranslate WordPress plugin, affecting versions < 2.9.9. 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.9.9; sites on affected versions should update now. Disclosed March 2022, reported by Diogo Real.

Vulnerability Overview

The Translate WordPress with GTranslate <= 2.9.8 & Translate WordPress – Google Language Translator <= 6.0.13 WordPress plugins do not have proper capabilities checks in the /wp-content/plugins/gtranslate/url_addon/gtranslate.php file which writes debug data such as user's cookies in a publicly accessible file when the enable_debug parameter is set to true. This would make it possible for an attacker to steal and administrators cookies if they can successfully trick them into accessing that file with the parameter set.

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-862: Missing Authorization

Reaching this weakness in Translate WordPress with GTranslate < 2.9.9 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Translate WordPress with GTranslate the fix is 2.9.9: builds < 2.9.9 are affected, anything from 2.9.9 onward is not.

Remediation

Update to version 2.9.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Translate WordPress with GTranslate 2.9.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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