CVE-2026-15005

Loco Translate <= 2.8.5 - Cross-Site Request Forgery to Remote Code Execution via 'template' Parameter

Published Jul 16, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
The Loco Translate plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8.5. This is due to missing or incorrect nonce validation on the execTemplate function. This makes it possible for unauthenticated attackers to execute arbitrary PHP code on the server by supplying a php://filter stream wrapper URI as the 'template' parameter, which bypasses path validation and is passed directly to the include sink in execTemplate() via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Analysis

AI-generated

Technical impact

The Loco Translate plugin for WordPress contains a Cross‑Site Request Forgery flaw in all releases up to and including version 2.8.5. The flaw arises from missing or incorrect nonce validation on the execTemplate function, allowing an unauthenticated attacker to supply a php://filter stream wrapper URL as the 'template' parameter. This URL is passed directly into an include call, which can result in arbitrary PHP code execution on the server. The weakness is classified as CWE‑352.

Affected Systems

The vulnerability affects the WordPress Loco Translate plugin developed by Tim Whitlock, specifically every version numbered 2.8.5 or earlier. Any WordPress site that has this plugin installed and active is susceptible, regardless of the rest of the site configuration.

Risk and Exploitability

The CVSS base score of 8.8 indicates high severity, while the EPSS score of <1% points to a low probability of exploitation at the present time. The vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a CSRF attack that requires a site administrator or other privileged user to unknowingly submit the crafted request, such as clicking a malicious link. Because the exploit depends on user interaction, the chance of automated exploitation is low, but the impact on a successful attack is total loss of code execution control over the affected WordPress installation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Loco Translate plugin to the latest version that includes nonce validation on execTemplate.
  • If the plugin is not essential, disable or remove it entirely from the WordPress installation.
  • Restrict administrator access to trusted IP addresses or use two‑factor authentication to limit the risk of a forged request being submitted.

Generated by OpenCVE AI on July 31, 2026 at 02:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Timwhitlock
Timwhitlock loco Translate
Wordpress
Wordpress wordpress
Vendors & Products Timwhitlock
Timwhitlock loco Translate
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Description The Loco Translate plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8.5. This is due to missing or incorrect nonce validation on the execTemplate function. This makes it possible for unauthenticated attackers to execute arbitrary PHP code on the server by supplying a php://filter stream wrapper URI as the 'template' parameter, which bypasses path validation and is passed directly to the include sink in execTemplate() via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Title Loco Translate <= 2.8.5 - Cross-Site Request Forgery to Remote Code Execution via 'template' Parameter
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Jul 16, 2026, 12:26 PM
Reserved
Jul 7, 2026, 8:30 PM
Status
Deferred
Published
Jul 16, 2026, 9:16 AM
Modified
Jul 16, 2026, 1:38 PM