Loco Translate <= 2.8.2 - Authenticated (Translator+) Path Traversal to Limited File Read via 'ref' Parameter
| CVE | CVE-2026-1921 |
|---|---|
| CVSS | 4.9 (Medium) |
| Publicly Published | May 4, 2026 |
| Last Updated | May 5, 2026 |
| Researcher |
shark3y
|
Description
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.
References
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
- plugins.trac.wordpress.org
Share
Vulnerability Details for Loco Translate
| Software Type | Plugin |
|---|---|
| Software Slug | loco-translate (view on wordpress.org) |
| Patched? | Yes |
| Remediation | Update to version 2.8.3, or a newer patched version |
| Affected Version |
|
| Patched Version |
|
Recent vulnerabilities in Loco Translate
| # | Title | CVE ID | CVSS | Researchers | Date |
|---|---|---|---|---|---|
| 1 | Loco Translate <= 2.8.5 - Cross-Site Request Forgery to Remote Code Execution via 'template' Parameter | CVE-2026-15005 | mikemyers | July 15, 2026 | |
| 2 | Loco Translate <= 2.8.2 - Reflected Cross-Site Scripting via 'update_href' Parameter | CVE-2026-4146 | AlexHenry | March 30, 2026 | |
| 3 | Loco Translate <= 2.6.9 - Cross-Site Request Forgery | CVE-2024-37236 | Nosa "apapedulimu" Shandy | June 21, 2024 | |
| 4 | Loco Translate <= 2.6.0 - Authenticated Stored Cross-Site Scripting | CVE-2022-0765 | Taurus Omar | March 22, 2022 | |
| 5 | Loco Translate <= 2.5.3 - Authenticated PHP Code Injection | CVE-2021-24721 | Tomi Ashari | October 11, 2021 |
This record contains material that is subject to copyright.
Copyright 2012-2026 Defiant Inc.
License: Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy. Read more.
Copyright 1999-2026 The MITRE Corporation
License: CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy. Read more.
Have information to add, or spot any errors? Contact us at wfi-support@wordfence.com so we can make any appropriate adjustments.
Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!
Learn moreWant to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.
The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.
Documentation