Backup, Restore and Migrate WordPress Sites With the XCloner Plugin <= 3.1.4 - Path Traversal to Sensitive Information Disclosure

2016-12-31 00:00
Anonymous

Strategic Overview

Status
Patched in 3.1.5
Affected Version
<= 3.1.4
CVSS
4.3Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE pending
View all Backup, Restore and Migrate your sites with XCloner vulnerabilities

At a glance

This record tracks a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Backup, Restore and Migrate your sites with XCloner WordPress plugin, affecting versions <= 3.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 3.1.5; sites on affected versions should update now. Disclosed December 2016.

Vulnerability Overview

The XCloner plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 3.1.4 via leaked directory listings from the 'files_xml.' AJAX action. This can allow authenticated attackers to extract sensitive data including otherwise private filepaths and backups.

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-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Backup, Restore and Migrate your sites with XCloner <= 3.1.4 takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Backup, Restore and Migrate your sites with XCloner the fix is 3.1.5: builds <= 3.1.4 are affected, anything from 3.1.5 onward is not.

Remediation

Update to version 3.1.5, 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 3.1.5 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