CVE-2022-0765

Loco Translate <= 2.6.0 - Authenticated Stored Cross-Site Scripting

2022-03-22 00:00
Taurus Omar

Strategic Overview

Status
Patched in 2.6.1
Affected Plugin
Loco Translate
Affected Version
< 2.6.1
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-0765
View all Loco Translate vulnerabilities

At a glance

CVE-2022-0765 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Loco Translate WordPress plugin, affecting versions < 2.6.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.6.1; sites on affected versions should update now. Disclosed March 2022, reported by Taurus Omar.

Vulnerability Overview

The Loco Translate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via elements in versions up to, and including, 2.6.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with access to the plugin, such as translators and site administrators, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Loco Translate < 2.6.1 takes any authenticated account. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Loco Translate the fix is 2.6.1: builds < 2.6.1 are affected, anything from 2.6.1 onward is not.

Remediation

Update to version 2.6.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Loco Translate: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Loco Translate 2.6.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-0765https://www.wordfence.com/threat-intel/vulnerabilities/id/4d3b1a76-febc-4037-b31e-5987f8a23e92https://nvd.nist.gov/vuln/detail/CVE-2022-0765

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C