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.
References7
- plugins.trac.wordpress.org/browser/loco-translate/tags/2.8.1/sr…
- plugins.trac.wordpress.org/browser/loco-translate/tags/2.8.1/sr…
- plugins.trac.wordpress.org/browser/loco-translate/trunk/src/aja…
- plugins.trac.wordpress.org/browser/loco-translate/trunk/src/aja…
- plugins.trac.wordpress.org/changeset/3482475/loco-translate/tru…
- plugins.trac.wordpress.org/changeset?old_path=%2Floco-translate…
- www.wordfence.com/threat-intel/vulnerabilities/id/f9ff3058-a08c…
Metrics
- CVSS 3.1
-
4.9
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 1% percentile: 51 · as of 13 November 2026
- CWE
- CWE-22
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.