CVE-2021-24610

TranslatePress <= 2.0.8 - Authenticated Stored Cross-Site Scripting

2021-08-30 00:00
apapedulimu

Strategic Overview

Status
Patched in 2.0.9
Affected Version
< 2.0.9
CVSS
4.8Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24610
View all TranslatePress – Translate Multilingual sites with AI Translation vulnerabilities

At a glance

CVE-2021-24610 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the TranslatePress WordPress plugin, affecting versions < 2.0.9. It carries a CVSS score of 4.8 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.0.9; sites on affected versions should update now. Disclosed August 2021, reported by apapedulimu.

Vulnerability Overview

The TranslatePress WordPress plugin before 2.0.9 does not implement a proper sanitisation on the translated strings. The 'trp_sanitize_string' function only removes script tag with a regex, still allowing other HTML tags and attributes to execute javascript, which could lead to authenticated Stored Cross-Site Scripting issues.

Technical Analysis

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

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

TranslatePress < 2.0.9 carries this weakness at trp_sanitize_string, and reaching it 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 TranslatePress the fix is 2.0.9: builds < 2.0.9 are affected, anything from 2.0.9 onward is not.

Remediation

Update to version 2.0.9, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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