WPML <= 4.6.0 - Reflected Cross-Site Scripting via wp_lang

2023-04-16 00:00
Deepak kumar

Strategic Overview

Status
Patched in 4.6.1
Affected Plugin
WPML Multilingual CMS
Affected Version
<= 4.6.0
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all WPML Multilingual CMS vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WPML Multilingual CMS WordPress plugin, affecting versions <= 4.6.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.6.1; sites on affected versions should update now. Disclosed April 2023, reported by Deepak kumar.

Vulnerability Overview

The WPML plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the wp_lang parameter in versions up to, and including, 4.6.0 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 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 privileges on the target site.

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

Reaching this weakness in WPML Multilingual CMS <= 4.6.0 takes a caller who can reach the endpoint. 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 WPML Multilingual CMS the fix is 4.6.1: builds <= 4.6.0 are affected, anything from 4.6.1 onward is not.

Remediation

Update to version 4.6.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/2b2302d9-426c-415b-a7d3-3a9de95d87d1

Related records

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