CVE-2025-11759
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-11759 is a Cross-Site Request Forgery (CSRF) vulnerability in the "Backup, Restore and Migrate your sites with XCloner" plugin for WordPress. It affects all versions up to and including 4.8.2, and was published on December 5, 2025, with Wordfence as the assigning CNA. The flaw allows unauthenticated attackers to modify FTP backup configurations by tricking a site administrator into clicking a malicious link. It carries a CVSS v3.1 base score of 4.3 (Medium) (Wordfence, Red Hat CVE).

Technical details

The vulnerability is classified as CWE-352 (Cross-Site Request Forgery) and stems from missing or incorrect nonce validation in the Xcloner_Remote_Storage::save() function within the XCloner plugin. Because this function does not properly verify the origin of requests, an attacker can craft a forged HTTP request that, when triggered by an authenticated administrator, modifies the plugin's remote storage configuration — specifically the FTP backup destination. No authentication or elevated privileges are required on the attacker's side; only user interaction (administrator clicking a link) is needed (Wordfence, WordPress Trac).

Impact

Successful exploitation allows an attacker to redirect WordPress site backups to an attacker-controlled FTP server, enabling exfiltration of potentially sensitive site data including database contents, configuration files, and user information. The integrity impact is limited to modification of the backup storage configuration, with no direct confidentiality or availability impact scored by the CVSS vector. However, the secondary consequence — backup data exfiltration — represents a significant real-world confidentiality risk for affected WordPress sites (Wordfence).

Exploitability

There is no evidence of active in-the-wild exploitation or public proof-of-concept exploit code at this time. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.013% (0.000130), indicating a very low probability of exploitation in the near term (Feedly). Exploitation requires social engineering to trick a logged-in WordPress administrator into interacting with a malicious link or page.

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the XCloner plugin version 4.8.2 or earlier using tools like WPScan or by inspecting publicly accessible plugin metadata.
  2. Craft malicious request: Construct a forged HTTP POST request targeting the Xcloner_Remote_Storage::save() function endpoint, embedding attacker-controlled FTP server credentials (host, username, password) as parameters.
  3. Deliver payload: Host the forged request in a malicious HTML page (e.g., an auto-submitting form) and deliver the link to a WordPress site administrator via phishing email, comment, or other social engineering vector.
  4. Administrator triggers CSRF: When the administrator visits the malicious page while authenticated to the WordPress admin panel, the browser automatically submits the forged request, updating the FTP backup configuration to point to the attacker's server.
  5. Exfiltrate backup data: Wait for the next scheduled or manually triggered backup; the XCloner plugin will upload the site backup (including database and files) to the attacker-controlled FTP server (Wordfence).

Indicators of compromise

  • Logs: WordPress admin action logs or server access logs showing unexpected POST requests to the XCloner remote storage save endpoint from unusual referrer URLs or IP addresses.
  • Configuration: XCloner plugin FTP backup settings changed to an unrecognized or external FTP host, username, or IP address — detectable via the WordPress admin panel under XCloner remote storage settings.
  • Network: Outbound FTP connections (port 21) from the WordPress server to unfamiliar external IP addresses, particularly coinciding with backup schedule times.
  • File System: Backup archive files (e.g., .tar.gz, .zip) missing from the expected local backup directory after a backup job completes, suggesting successful transfer to a remote destination.

Mitigation and workarounds

Users should update the XCloner plugin to version 4.8.3 or later, which addresses the missing nonce validation in the Xcloner_Remote_Storage::save() function. The fix is documented in the WordPress plugin repository changeset (WordPress Trac). As an interim measure, administrators should avoid clicking links from untrusted sources while logged into the WordPress admin panel, and consider temporarily disabling the XCloner remote storage feature until the update is applied.

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2024-13784CRITICAL9.8
  • arforms-form-builder
NoYesAug 16, 2026
CVE-2026-17087HIGH7.5
  • wp-travel-engine
NoYesAug 16, 2026
CVE-2026-2497HIGH7.2
  • gallery-plugin
NoYesAug 16, 2026
CVE-2026-17608MEDIUM6.5
  • wp-compress-image-optimizer
NoYesAug 16, 2026
CVE-2026-2357MEDIUM6.4
  • bold-page-builder
NoYesAug 16, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management