CVE-2025-11759

Backup, Restore and Migrate your sites with XCloner <= 4.8.2 - Cross-Site Request Forgery in Xcloner_Remote_Storage:save()

2025-12-04 13:31
Rafshanzani Suhada

Strategic Overview

Status
Patched in 4.8.3
Affected Plugin
Backup, Restore and Migrate your sites with XCloner
Affected Version
<= 4.8.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-11759
View all Backup, Restore and Migrate your sites with XCloner vulnerabilities

At a glance

CVE-2025-11759 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Backup, Restore and Migrate your sites with XCloner WordPress plugin, affecting versions <= 4.8.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.8.3; sites on affected versions should update now. Disclosed December 2025, reported by Rafshanzani Suhada.

Vulnerability Overview

The Backup, Restore and Migrate your sites with XCloner plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.8.2. This is due to missing or incorrect nonce validation on the Xcloner_Remote_Storage:save() function. This makes it possible for unauthenticated attackers to add or modify an FTP backup configuration via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Successful exploitation allows an attacker to set an attacker-controlled FTP site for backup storage and exfiltrate potentially sensitive site data.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Backup, Restore and Migrate your sites with XCloner <= 4.8.2 carries this weakness at save(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Backup, Restore and Migrate your sites with XCloner the fix is 4.8.3: builds <= 4.8.2 are affected, anything from 4.8.3 onward is not.

Remediation

Update to version 4.8.3, 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 4.8.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-11759https://www.wordfence.com/threat-intel/vulnerabilities/id/a76a8e36-635a-48a3-8683-c24a0395212ehttps://nvd.nist.gov/vuln/detail/CVE-2025-11759

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C