dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4146

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Reflected Cross-Site Scripting via the ‘update_href’ parameter in all versions up to, and including, 2.8.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user 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.2 contain a reflected Cross-Site Scripting vulnerability in the 'update_href' parameter. Insufficient input sanitization and inadequate output escaping allow unauthenticated attackers to inject arbitrary JavaScript through malicious URLs. Successful exploitation requires social engineering to trick users into clicking crafted links.

MitigationUpdate to the latest version of Loco Translate when available, or apply a WAF rule to sanitize the 'update_href' parameter and block XSS payloads until the patch can be applied.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 panel and navigate to Plugins > Installed Plugins. Search for 'Loco Translate' in the list of active plugins.
    Affected if The Loco Translate plugin appears in the installed plugins list
  2. Identify installed plugin version
    In the plugins list, locate the version number displayed beneath the Loco Translate plugin name. Alternatively, access the plugin directory via FTP or file manager and open the main plugin file (usually loco-translate.php) to find the version definition.
    Affected if The version number is 2.8.2 or lower
  3. Check if update_href parameter is accessible
    Review your web server access logs (Apache, Nginx, or WAF logs) for requests containing 'update_href' as a URL parameter. Alternatively, use browser developer tools to inspect network requests when accessing Loco Translate admin pages.
    Affected if The 'update_href' parameter is being processed by the application without sanitization (raw parameter values appear in responses)
  4. Inspect the vulnerable code path
    If you have file access, locate the Loco Translate plugin file handling the update_href parameter (typically in admin/views or similar directories). Search for the code that processes this parameter and verify whether proper escaping (esc_attr, esc_html) or sanitization is applied before output.
    Affected if The code outputs the update_href parameter without using WordPress escape functions like esc_attr() or esc_html()

Your environment is affected if Loco Translate plugin is installed with version 2.8.2 or lower and the plugin's admin pages handling the update_href parameter are accessible.

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 the latest version of Loco Translate when available, or apply a WAF rule to sanitize the 'update_href' parameter and block XSS payloads until the patch can be applied.

Recommended fix Moderate confidence

Loco Translate version 2.8.3 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Loco Translate plugin
  4. Check the current version number
  5. Update the plugin to the latest available version (likely 2.8.3 or later)

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4146 — 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-4146 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