Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-35948: An issue was discovered in the XCloner Backup and Restore plugin before 4.2.13 for WordPress

64
This week
CRITICAL 9.9UPGRADE

CVE-2020-35948 is a critical-severity flaw (CVSS 9.9) affecting xcloner. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • EPSS top 2%: very likely to be exploited
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score9.9 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance24.9% (top 2%)
CISA exploited listNo
WeaknessCWE-863
Published2021-01-01
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: xcloner

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

xcloner xcloner UPGRADE
Affected: >= 4.2.1 and < 4.2.13
Fixed in: 4.2.13
Safe to downgrade to: a release before 4.2.1
1. Check installed version
apt-cache policy xcloner || rpm -q xcloner || xcloner --version
2. UPGRADE to 4.2.13 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade xcloner
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade xcloner
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.2.1 (Debian / Ubuntu)
apt-cache madison xcloner sudo apt install xcloner=<VERSION_BEFORE_4.2.1> sudo apt-mark hold xcloner
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list xcloner sudo dnf downgrade xcloner-<VERSION_BEFORE_4.2.1> sudo dnf versionlock add xcloner
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-35948?

xcloner: upgrade to 4.2.13. Exact commands for each OS are on this page.

Is CVE-2020-35948 being exploited?

CVE-2020-35948 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-35948 affect?

CVE-2020-35948 affects xcloner. Severity is critical (CVSS 9.9). 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 cod

How urgent is CVE-2020-35948?

Priority 64/100. Critical severity; EPSS top 2%: very likely to be exploited; Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.