WordPress security changelog
MEDIUM CVE-2014-8603 Modified

Xcloner: A security weakness

Xcloner is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 6.5 CVSS · cve@mitre.org
NVD score 6.5 CVSS 2.0 · nvd@nist.gov
Component
Xcloner
Plugin slug
xcloner
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jun 10, 2015
Weakness
CWE-20 — Improper Input Validation

This CVE was published Jun 10, 2015 and is one of 12 known issues for this plugin.

Update, patch or deactivate.

Update Xcloner to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

cloner.functions.php in the XCloner plugin 3.1.1 for WordPress and 3.5.1 for Joomla! allows remote administrators to execute arbitrary code via shell metacharacters in the (1) file name when creating a backup or vectors related to the (2) $_CONFIG[tarpath], (3) $exclude, (4) $_CONFIG['tarcompress'], (5) $_CONFIG['filename'], (6) $_CONFIG['exfile_tar'], (7) $_CONFIG[sqldump], (8) $_CONFIG['mysql_host'], (9) $_CONFIG['mysql_pass'], (10) $_CONFIG['mysql_user'], (11) $database_name, or (12) $sqlfile variable.

NVD vector: AV:N/AC:L/Au:S/C:P/I:P/A:P

Primary and upstream sources