CVE-2026-1921

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

2026-05-04 13:32
shark3y

Strategic Overview

Status
Patched in 2.8.3
Affected Plugin
Loco Translate
Affected Version
<= 2.8.2
CVSS
4.9Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-1921
View all Loco Translate vulnerabilities

At a glance

CVE-2026-1921 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Loco Translate WordPress plugin, affecting versions <= 2.8.2. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Translator level or above. The issue is fixed in version 2.8.3; sites on affected versions should update now. Disclosed May 2026, reported by shark3y.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

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

Loco Translate <= 2.8.2 carries this weakness at findSourceFile(), and reaching it takes an account at Translator level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Loco Translate the fix is 2.8.3: builds <= 2.8.2 are affected, anything from 2.8.3 onward is not.

Remediation

Update to version 2.8.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Translator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Loco Translate 2.8.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1921https://www.wordfence.com/threat-intel/vulnerabilities/id/f9ff3058-a08c-40ed-b756-81e703b2277ahttps://nvd.nist.gov/vuln/detail/CVE-2026-1921

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C