Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 06 May 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 05 May 2026 05:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Timwhitlock
Timwhitlock loco Translate Wordpress Wordpress wordpress |
|
| Vendors & Products |
Timwhitlock
Timwhitlock loco Translate Wordpress Wordpress wordpress |
Tue, 05 May 2026 02:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Loco Translate <= 2.8.2 - Authenticated (Translator+) Path Traversal to Limited File Read via 'ref' Parameter | |
| Weaknesses | CWE-22 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: Wordfence
Published:
Updated: 2026-05-06T12:27:43.824Z
Reserved: 2026-02-04T17:33:59.876Z
Link: CVE-2026-1921
Updated: 2026-05-06T12:27:40.938Z
Status : Deferred
Published: 2026-05-05T03:15:59.100
Modified: 2026-05-05T19:09:32.000
Link: CVE-2026-1921
No data.
OpenCVE Enrichment
Updated: 2026-05-05T05:00:06Z