Loco Translate: Translator-level file disclosure outside the web root
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. The authoritative export does not name the individual route, parameter or permitted file types. The authoritative export identifies the fixed release as 2.8.9.
- Component
- Loco Translate
- Plugin slug
loco-translate- Affected
- < 2.8.9
- Safe version
2.8.9- Published
- Oct 03, 2026
This CVE was published Oct 03, 2026 and is one of 9 known issues for this plugin.
Update, patch or deactivate.
Update Loco Translate to 2.8.9 or a later supported release. An application-level fix should canonicalize requested translation paths and enforce an allowlisted translation root and file-type policy before reading; reject traversal and paths outside that root.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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 / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N