CVE-2020-35950

Backup, Restore and Migrate WordPress Sites With the XCloner Plugin <= 4.2.152 - Cross-Site Request Forgery

2020-08-18 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 4.2.153
Affected Version
< 4.2.153
CVSS
9.8Critical
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2020-35950
View all Backup, Restore and Migrate your sites with XCloner vulnerabilities

At a glance

CVE-2020-35950 is a critical-severity Cross-Site Request Forgery (CSRF) vulnerability in the Backup, Restore and Migrate your sites with XCloner WordPress plugin, affecting versions < 4.2.153. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.2.153; sites on affected versions should update now. Disclosed August 2020, reported by Chloe Chamberland.

Vulnerability Overview

An issue was discovered in the XCloner Backup and Restore plugin before 4.2.153 for WordPress. It allows CSRF (via almost any endpoint).

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, and no interaction from a victim user. 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 Backup, Restore and Migrate your sites with XCloner < 4.2.153 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 Backup, Restore and Migrate your sites with XCloner the fix is 4.2.153: builds < 4.2.153 are affected, anything from 4.2.153 onward is not.

Remediation

Update to version 4.2.153, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Backup, Restore and Migrate your sites with XCloner: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Backup, Restore and Migrate your sites with XCloner 4.2.153 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