CVE-2020-10568

WPML < 4.3.7 - Cross-Site Request Forgery Bypass

2020-03-09 00:00
Gerard Arall

Strategic Overview

Status
Patched in 4.3.7
Affected Plugin
WPML Multilingual CMS
Affected Version
< 4.3.7
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2020-10568
View all WPML Multilingual CMS vulnerabilities

At a glance

CVE-2020-10568 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPML Multilingual CMS WordPress plugin, affecting versions < 4.3.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.3.7; sites on affected versions should update now. Disclosed March 2020, reported by Gerard Arall.

Vulnerability Overview

The sitepress-multilingual-cms (WPML) plugin before 4.3.7 for WordPress has CSRF due to a loose comparison. This leads to remote code execution in includes/class-wp-installer.php via a series of requests that leverage unintended comparisons of integers to strings.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WPML Multilingual CMS < 4.3.7 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WPML Multilingual CMS the fix is 4.3.7: builds < 4.3.7 are affected, anything from 4.3.7 onward is not.

Remediation

Update to version 4.3.7, 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.3.7 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