dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-15005

HIGH · 8.8 CVSS v3.1 Published 2026-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Loco Translate WordPress plugin (versions up to 2.8.5) lacks proper nonce validation on the execTemplate function, allowing CSRF attacks. By tricking an authenticated administrator into clicking a malicious link, attackers can supply a php://filter stream wrapper URI as the 'template' parameter, bypassing path validation and passing it directly to an include() sink, enabling arbitrary PHP code execution.

MitigationUpdate to version 2.8.6 or later when available; implement proper nonce validation on the execTemplate function and sanitize/validate the template parameter to block php:// and other stream wrappers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Loco Translate plugin is installed
    Log into WordPress admin and go to Plugins > Installed Plugins, or run `wp plugin list` via WP-CLI, and look for 'Loco Translate' in the list
    Affected if Loco Translate appears in the installed plugins list
  2. Verify the installed version number
    In WordPress admin, click on the Loco Translate plugin to view its details and read the version number from the description; or check the plugin main file (usually loco-translate/loco.php) for the 'Version' header comment
    Affected if Version displayed is 2.8.5 or lower
  3. Confirm the plugin is active
    In WordPress admin under Plugins > Installed Plugins, check if Loco Translate shows 'Active' status; or run `wp plugin status loco-translate` via WP-CLI
    Affected if The plugin is active and version is 2.8.5 or earlier
  4. Identify the vulnerable execTemplate file
    Check if the file containing execTemplate function exists in the plugin directory, typically at loco-translate/src/ajax/helpers.php or similar path within the plugin folder
    Affected if The vulnerable file exists and the plugin version is 2.8.5 or earlier

You are affected if Loco Translate plugin version 2.8.5 or earlier is installed and active on your WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.8.6 or later when available; implement proper nonce validation on the execTemplate function and sanitize/validate the template parameter to block php:// and other stream wrappers.

Recommended fix Moderate confidence

Loco Translate version 2.8.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Loco Translate plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, manually download the updated plugin from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version is 2.8.6 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15005 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data