HomeWordPress vulnerabilitiesTranslate WordPress
Translate WordPress vulnerabilities
Translate WordPress has 3 known vulnerabilities in this database. The most recent published record is dated 16 Oct 2024.
- Known vulnerabilities
- 3
- Active installs
- 100,000+
- Latest version
- 7.0.1
- Last updated
- 11 Sep 2026
- Most recent
- 16 Oct 2024
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2021-4452 | High 7.1 | Up to 6.0.9 | Fixed in a later version (latest 7.0.1) | 16 Oct 2024 |
| Cross-site scripting (XSS) CVE-2021-24594 | Medium 4.8 | Before 6.0.12 | Fixed in 6.0.12 | 8 Nov 2021 |
| Cross-site scripting (XSS) CVE-2016-10870 | Medium 6.1 | Before 5.0.06 | Fixed in 5.0.06 | 13 Aug 2019 |
Read the published descriptions
- CVE-2021-4452, 16 Oct 2024
- The Google Language Translator plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via multiple parameters in versions up to, and including, 6.0.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Specifically affects users with older browsers that lack proper URL encoding support. CVE record
- CVE-2021-24594, 8 Nov 2021
- The Translate WordPress - Google Language Translator WordPress plugin before 6.0.12 does not sanitise and escape some of its settings before outputting it in various pages, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed. CVE record
- CVE-2016-10870, 13 Aug 2019
- The google-language-translator plugin before 5.0.06 for WordPress has XSS. CVE record
What to do if you run Translate WordPress
If you run Translate WordPress, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Translate WordPress vulnerabilities
Free. We email you when a new vulnerability is published for Translate WordPress, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.