CVE-2026-1921: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in timwhitlock Loco Translate
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.
AI Analysis
Technical Summary
CVE-2026-1921 is a path traversal vulnerability (CWE-22) in the Loco Translate plugin for WordPress, affecting all versions up to 2.8.2. The vulnerability exists in the findSourceFile() method, which normalizes user-supplied 'ref' paths without ensuring the resolved path remains within the allowed bundle or content directories. This allows authenticated users with Translator-level or higher privileges to read arbitrary .php, .js, .json, and .twig files on the server filesystem outside the intended directory. The wp-config.php file is specifically excluded from access. The vulnerability does not require user interaction and has a CVSS 3.1 base score of 4.9 (medium severity). No official patch or remediation level is currently documented.
Potential Impact
An authenticated attacker with Translator-level or higher privileges can read arbitrary files on the server outside the intended translation directories, potentially exposing sensitive information contained in .php, .js, .json, and .twig files. However, critical files such as wp-config.php are excluded from access. There is no indication of impact on integrity or availability, only confidentiality is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Translator-level access to trusted users only. Monitor for updates from the vendor or plugin maintainers regarding patches or official mitigations.
CVE-2026-1921: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in timwhitlock Loco Translate
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.
CVSS v3.1
Score 4.9medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-1921 is a path traversal vulnerability (CWE-22) in the Loco Translate plugin for WordPress, affecting all versions up to 2.8.2. The vulnerability exists in the findSourceFile() method, which normalizes user-supplied 'ref' paths without ensuring the resolved path remains within the allowed bundle or content directories. This allows authenticated users with Translator-level or higher privileges to read arbitrary .php, .js, .json, and .twig files on the server filesystem outside the intended directory. The wp-config.php file is specifically excluded from access. The vulnerability does not require user interaction and has a CVSS 3.1 base score of 4.9 (medium severity). No official patch or remediation level is currently documented.
Potential Impact
An authenticated attacker with Translator-level or higher privileges can read arbitrary files on the server outside the intended translation directories, potentially exposing sensitive information contained in .php, .js, .json, and .twig files. However, critical files such as wp-config.php are excluded from access. There is no indication of impact on integrity or availability, only confidentiality is affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Translator-level access to trusted users only. Monitor for updates from the vendor or plugin maintainers regarding patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-04T17:33:59.876Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f95b2ccbff5d861087955a
Added to database: 5/5/2026, 2:51:24 AM
Last enriched: 5/12/2026, 6:19:48 AM
Last updated: 6/18/2026, 7:56:54 PM
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.