Loco Translate

loco-translate

total installs

1,000,000

total vulns

critical

high

medium

low

latest vuln

—

patched

unpatched

avg time to patch

—

vulnerabilities (2)

Loco Translate <= 2.8.2 - Authenticated (Translator+) Path Traversal to Limited File Read via 'ref' Parameter

medium ✓ patched

cve id CVE-2026-1921 ↗

cvss score 4.9

cwe CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

published May 4, 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.

Loco Translate <= 2.8.2 - Reflected Cross-Site Scripting via 'update_href' Parameter

medium ✓ patched

cve id CVE-2026-4146 ↗

cvss score 6.1

cwe CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

published Mar 30, 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.