Xcloner: Code execution
Xcloner is affected by code execution. Exploitation requires an authenticated WordPress account. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
- Component
- Xcloner
- Plugin slug
xcloner- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jan 01, 2021
This CVE was published Jan 01, 2021 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
An issue was discovered in the XCloner Backup and Restore plugin before 4.2.13 for WordPress. It gave authenticated attackers the ability to modify arbitrary files, including PHP files. Doing so would allow an attacker to achieve remote code execution. The xcloner_restore.php write_file_action could overwrite wp-config.php, for example. Alternatively, an attacker could create an exploit chain to obtain a database dump.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary and upstream sources
- NVD record for CVE-2020-35948
- Upstream reference packetstormsecurity.com
- GitHub upstream reference github.com
- Upstream reference wpscan.com
- Wordfence advisory wordfence.com
- Upstream reference packetstormsecurity.com
- GitHub upstream reference github.com
- Upstream reference wpscan.com
- Wordfence advisory wordfence.com