HomeWordPress vulnerabilitiesTranslate WordPress with GTranslate
Translate WordPress with GTranslate vulnerabilities
Translate WordPress with GTranslate has 5 known vulnerabilities in this database. The most recent published record is dated 11 Sep 2026.
- Known vulnerabilities
- 5
- Active installs
- 900,000+
- Latest version
- 5.0.1
- Last updated
- 15 Sep 2026
- Most recent
- 11 Sep 2026
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-2025-15695 | Low 3.5 | Before 3.0.10 | Fixed in 3.0.10 | 11 Sep 2026 |
| Cross-site scripting (XSS) CVE-2023-4502 | Medium 4.8 | Before 3.0.4 | Fixed in 3.0.4 | 25 Sep 2023 |
| Cross-site request forgery (CSRF) CVE-2022-0770 | High 8.8 | Before 2.9.9 | Fixed in 2.9.9 | 28 Mar 2022 |
| Cross-site scripting (XSS) CVE-2021-25103 | Medium 4.7 | Before 2.9.7 | Fixed in 2.9.7 | 7 Feb 2022 |
| Cross-site scripting (XSS) CVE-2020-11930 | Medium 6.1 | Before 2.8.52 | Fixed in 2.8.52 | 20 Apr 2020 |
Read the published descriptions
- CVE-2025-15695, 11 Sep 2026
- The Translate WordPress with GTranslate WordPress plugin before 3.0.10 does not validate one of its settings before the bundled front-end scripts build markup from it, allowing users with a role as high as administrator to store JavaScript that runs in the session of any visitor to the site. CVE record
- CVE-2023-4502, 25 Sep 2023
- The Translate WordPress with GTranslate WordPress plugin before 3.0.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). This vulnerability affects multiple parameters. CVE record
- CVE-2022-0770, 28 Mar 2022
- The Translate WordPress with GTranslate WordPress plugin before 2.9.9 does not have CSRF check in some files, and write debug data such as user's cookies in a publicly accessible file if a specific parameter is used when requesting them. Combining those two issues, an attacker could gain access to a logged in admin cookies by making them open a malicious link or page CVE record
- CVE-2021-25103, 7 Feb 2022
- The Translate WordPress with GTranslate WordPress plugin before 2.9.7 does not sanitise and escape the body parameter in the url_addon/gtranslate-email.php file before outputting it back in the page, leading to a Reflected Cross-Site Scripting issue. Note: exploitation of the issue requires knowledge of the NONCE_SALT and NONCE_KEY CVE record
- CVE-2020-11930, 20 Apr 2020
- The GTranslate plugin before 2.8.52 for WordPress has Reflected XSS via a crafted link. This requires use of the hreflang tags feature within a sub-domain or sub-directory paid option. CVE record
What to do if you run Translate WordPress with GTranslate
If you run Translate WordPress with GTranslate, 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 with GTranslate vulnerabilities
Free. We email you when a new vulnerability is published for Translate WordPress with GTranslate, 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.