HomeWordPress vulnerabilitiesLoco Translate
Loco Translate vulnerabilities
Loco Translate has 8 known vulnerabilities in this database. The most recent published record is dated 3 Oct 2026.
- Known vulnerabilities
- 8
- Active installs
- 1m+
- Latest version
- 2.8.9
- Last updated
- 30 Sep 2026
- Most recent
- 3 Oct 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 |
|---|---|---|---|---|
| Path traversal CVE-2026-94238 | Medium 6.8 | Before 2.8.9 | Fixed in 2.8.9 | 4 d ago |
| Cross-site scripting (XSS) CVE-2026-94239 | Medium 6.8 | Before 2.8.9 | Fixed in 2.8.9 | 4 d ago |
| Cross-site scripting (XSS) CVE-2026-15066 | Medium 6.4 | Up to 2.8.7 | Fixed in a later version (latest 2.8.9) | 16 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2026-15005 | High 8.8 | Up to 2.8.5 | Fixed in a later version (latest 2.8.9) | 16 Jul 2026 |
| Path traversal CVE-2026-1921 | Medium 4.9 | Up to 2.8.2 | Fixed in a later version (latest 2.8.9) | 5 May 2026 |
| Cross-site scripting (XSS) CVE-2026-4146 | Medium 6.1 | Up to 2.8.2 | Fixed in a later version (latest 2.8.9) | 31 Mar 2026 |
| Cross-site scripting (XSS) CVE-2022-0765 | Medium 5.4 | Before 2.6.1 | Fixed in 2.6.1 | 18 Apr 2022 |
| Remote code execution CVE-2021-24721 | Medium 6.5 | Before 2.5.4 | Fixed in 2.5.4 | 8 Nov 2021 |
Read the published descriptions
- CVE-2026-94238, 3 Oct 2026
- The Loco Translate WordPress plugin before 2.8.9 does not restrict which file paths its translation file routes will read, allowing users granted the Loco Translate WordPress plugin before 2.8.9's translator capability to retrieve the contents of files of certain types from anywhere on the server, including outside the web root. CVE record
- CVE-2026-94239, 3 Oct 2026
- The Loco Translate WordPress plugin before 2.8.9 does not sanitise and escape some bundle configuration values before outputting them back in an admin page, allowing users with the translator capability and above to perform Stored Cross-Site Scripting attacks against high privilege users such as administrators. CVE record
- CVE-2026-15066, 16 Aug 2026
- The Loco Translate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via PO File Extracted Comments in all versions up to, and including, 2.8.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with translator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-15005, 16 Jul 2026
- The Loco Translate plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8.5. This is due to missing or incorrect nonce validation on the execTemplate function. This makes it possible for unauthenticated attackers to execute arbitrary PHP code on the server by supplying a php://filter stream wrapper URI as the 'template' parameter, which bypasses path validation and is passed directly to the include sink in execTemplate() via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2026-1921, 5 May 2026
- The Loco Translate plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 2.8.2 via the `fsReference` AJAX route. This is due to the `findSourceFile()` method normalizing user-supplied `ref` paths containing `../` directory traversal sequences without validating that the resolved path remains within the intended bundle or content directory. This makes it possible for authenticated attackers, with Translator-level access and above (custom `loco_admin` capability required, granted to the `translator` role and administrators by default), to read arbitrary `.php`, `.js`, `.json`, and `.twig` files from the server filesystem outside the intended translation directory. Files named wp-config.php are excluded. CVE record
- CVE-2026-4146, 31 Mar 2026
- The Loco Translate plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘update_href’ parameter in all versions up to, and including, 2.8.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated 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. CVE record
- CVE-2022-0765, 18 Apr 2022
- The Loco Translate WordPress plugin before 2.6.1 does not properly remove inline events from elements in the source translation strings before outputting them in the editor in the plugin admin panel, allowing any user with access to the plugin (Translator and Administrator by default) to add arbitrary javascript payloads to the source strings leading to a stored cross-site scripting (XSS) vulnerability. CVE record
- CVE-2021-24721, 8 Nov 2021
- The Loco Translate WordPress plugin before 2.5.4 mishandles data inputs which get saved to a file, which can be renamed to an extension ending in .php, resulting in authenticated "translator" users being able to inject PHP code into files ending with .php in web accessible locations. CVE record
What to do if you run Loco Translate
If you run Loco Translate, 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 Loco Translate vulnerabilities
Free. We email you when a new vulnerability is published for Loco Translate, 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.