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

Q: How do I fix CVE-2020-35950?

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

Q: Is CVE-2020-35950 being exploited?

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

Q: What does CVE-2020-35950 affect?

CVE-2020-35950 affects xcloner. Severity is critical (CVSS 9.8). An issue was discovered in the XCloner Backup and Restore plugin before 4.2.153 for WordPress. It allows CSRF (via almost any endpoint).

Q: How urgent is CVE-2020-35950?

Priority 60/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-35950 is a critical-severity flaw (CVSS 9.8) 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.153 for WordPress. It allows CSRF (via almost any endpoint).

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-352
Published	2021-01-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: xcloner

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

Am I affected?

Timeline

2021-01-01 04:15 UTCPublished CVE record published
2026-06-17 03:14 UTCUpdated Record last modified

xcloner xcloner UPGRADE

Affected: < 4.2.153

Fixed in: 4.2.153

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy xcloner || rpm -q xcloner || xcloner --version

2. UPGRADE to 4.2.153 (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.

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-35950?

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

Is CVE-2020-35950 being exploited?

CVE-2020-35950 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-35950 affect?

CVE-2020-35950 affects xcloner. Severity is critical (CVSS 9.8). An issue was discovered in the XCloner Backup and Restore plugin before 4.2.153 for WordPress. It allows CSRF (via almost any endpoint).

How urgent is CVE-2020-35950?

Priority 60/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-0444 MEDIUM 4.3 UPGRADE The Backup, Restore and Migrate WordPress Sites With the XCloner Plugin WordPress plugin before 4.3.6 does not
CVE-2020-35948 CRITICAL 9.9 UPGRADE An issue was discovered in the XCloner Backup and Restore plugin before 4.2.13 for WordPress

References

← Back to latest CVEs