WordPress security by component
Google Language Translator
Plugin description
Google Language Translator is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Dec 09, 2024; the highest CVE/CNA score is 7.1.
Plugin slug:
google-language-translatorLatest vulnerability
CVE-2023-50375: Google Language Translator: A security weakness
Google Language Translator is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
| Safe version |
|
||
|---|---|---|---|
| Dec 09, 2024 |
CVE-2023-50375
Google Language Translator: A security weakness
Google Language Translator is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Oct 16, 2024 |
CVE-2021-4452
Google Language Translator: Cross-site scripting
Google Language Translator is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE7.1
NVD5.4
|
| Nov 08, 2021 |
CVE-2021-24594
Translate WordPress – Google Language Translator: Cross-site scripting
Translate WordPress – Google Language Translator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.8
NVD4.8
|
| Aug 13, 2019 |
CVE-2016-10870
Google Language Translator: Cross-site scripting
Google Language Translator is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.1
NVD6.1
|