Skip to main content
Vulnerability Database/CVE-2025-10579

CVE-2025-10579: BackWPup WordPress Plugin Auth Bypass Flaw

CVE-2025-10579 is an authentication bypass vulnerability in BackWPup WordPress Backup & Restore Plugin that lets authenticated attackers access backup filenames. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-10579 Overview

CVE-2025-10579 is an information disclosure vulnerability in the BackWPup – WordPress Backup & Restore Plugin for WordPress. The flaw affects all versions up to and including 5.5.0. The plugin fails to perform a capability check on the backwpup_working AJAX action. Authenticated users with Subscriber-level access or higher can retrieve a backup's filename while a backup is running. The disclosed filename has limited standalone value but can assist brute-force attempts to retrieve backup contents on specific server configurations such as NGINX. The issue is tracked as a missing authorization weakness [CWE-862].

Critical Impact

Low-privileged authenticated users can obtain in-progress backup filenames, which may enable retrieval of backup contents on misconfigured web servers.

Affected Products

  • BackWPup – WordPress Backup & Restore Plugin for WordPress
  • All versions up to and including 5.5.0
  • WordPress sites running the affected plugin, particularly those served by NGINX

Discovery Timeline

  • 2025-10-25 - CVE-2025-10579 published to the National Vulnerability Database (NVD)
  • 2026-10-08 - Last updated in NVD database

Technical Details for CVE-2025-10579

Vulnerability Analysis

The BackWPup plugin registers an AJAX action named backwpup_working used to report the status of backup jobs. The handler does not verify the caller's WordPress role or capabilities before returning job metadata. Any authenticated user, including accounts at the Subscriber level, can invoke the endpoint and read the filename of a backup that is currently being generated.

Filename disclosure alone does not expose backup contents. However, the plugin writes backup archives to a predictable location inside the WordPress uploads directory. On servers that do not restrict direct file access through .htaccess rules, such as default NGINX deployments, knowing the filename allows an attacker to request the archive directly over HTTP. The attack requires authentication but no user interaction and is remotely exploitable.

Root Cause

The root cause is a missing authorization check in the backwpup_working AJAX handler. WordPress plugin AJAX endpoints must call current_user_can() or an equivalent capability verification before returning sensitive job data. The pre-patch handler verified only that the request originated from an authenticated session, not that the session had administrative privileges to manage backups.

Attack Vector

An attacker with any authenticated WordPress account on the target site sends a POST request to /wp-admin/admin-ajax.php with the action parameter set to backwpup_working while a backup job is active. The response contains the backup filename. The attacker then attempts to download the file directly from the uploads directory. On NGINX servers without directory-level deny rules, the request succeeds and exposes the full site backup, which typically contains database contents and configuration secrets.

Technical details are documented in the WordPress Plugin Changeset, the CleanTalk CVE Analysis, and the Wordfence Vulnerability Report.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2025-10579

Indicators of Compromise

  • Unexpected POST requests to /wp-admin/admin-ajax.php carrying the parameter action=backwpup_working from Subscriber-level accounts.
  • HTTP GET requests from authenticated or unauthenticated clients targeting files inside /wp-content/uploads/backwpup-*/ with randomized archive names.
  • Repeated access attempts to backup directories within a short time window following plugin activity.

Detection Strategies

  • Audit web server access logs for admin-ajax.php calls where the action equals backwpup_working and correlate against the role of the authenticated user.
  • Monitor for direct file requests to the BackWPup uploads subdirectory and alert when the response status is 200 for archive extensions such as .zip, .tar.gz, or .sql.
  • Review WordPress user listings for low-privileged accounts created shortly before backup-related activity.

Monitoring Recommendations

  • Enable verbose request logging on the WordPress host and forward it to a centralized log platform for correlation.
  • Track plugin version inventory across all managed WordPress sites to confirm every instance is patched above 5.5.0.
  • Alert on new file downloads from the BackWPup directory that do not originate from administrator sessions.

How to Mitigate CVE-2025-10579

Immediate Actions Required

  • Update the BackWPup plugin to a version released after 5.5.0 that includes the authorization check fix.
  • Audit WordPress user accounts and remove or disable unused Subscriber-level accounts.
  • Restrict direct HTTP access to backup directories at the web server configuration layer.

Patch Information

The vendor addressed the vulnerability in the commit documented at the WordPress Plugin Changeset. The fix adds a capability check to the backwpup_working AJAX handler so that only users with backup management privileges receive job status data. Site administrators should install the latest release through the WordPress plugin updater.

Workarounds

  • Store BackWPup archives outside the web-accessible document root by configuring an alternate destination such as Amazon S3 or an off-site FTP target.
  • Add an NGINX location block that denies direct HTTP access to the BackWPup uploads subdirectory.
  • Temporarily disable the BackWPup plugin on sites that cannot be patched immediately and that run on NGINX without directory access controls.
bash
# NGINX configuration example to block direct access to BackWPup archives
location ~* /wp-content/uploads/backwpup-.*/ {
    deny all;
    return 403;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.