CVE-2025-10579
Description
The BackWPup – WordPress Backup & Restore Plugin plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'backwpup_working' AJAX action in all versions up to, and including, 5.5.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve access to a back-up's filename while a backup is running. This information has little value on it's own, but could be used to aid in a brute force attack to retrieve back-up contents in limited environments (i.e. NGINX).
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
BackWPup plugin ≤5.5.0 exposes backup filenames to authenticated low-privilege users via an unprotected AJAX action, aiding brute-force downloads of full archives.
Vulnerability
Overview
The BackWPup – WordPress Backup & Restore Plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'backwpup_working' AJAX action in all versions up to, up to and including, version 5.5.0.0 [1]. This flaw allows authenticated attackers with Subscriber-level access or above to retrieve the filename of a backup while it is running [1].
Exploitation and
Attack Surface
An attacker who is authenticated as a Subscriber (the lowest privileged role) can trigger the vulnerable AJAX endpoint to learn the exact filename of a newly generated backup archive [1]. The backup archives are stored in a web-served directory with a per-site random subfolder that is only six hex characters long, making it feasible to brute-force the full path once the filename is known [1]. This is particularly effective in environments using NGINX or similar configurations where directory listing is disabled but direct file access is allowed [1].
Impact
Impact
While the filename alone has limited value, it can be used to aid in a brute-force attack to retrieve the backup contents [1]. Backup archives often contain highly sensitive data, including database credentials from wp-config.php, authentication salts, plugin configuration tokens, and user password hashes [1]. Successful retrieval of a backup archive could lead to complete confidentiality compromise and enable an attacker to pivot to full administrative control of the WordPress site [1].
Mitigation
The vulnerability has been addressed in version 5.0.1 of the plugin [1]. Users are strongly advised to update to the latest patched version immediately. No workaround is available for older versions [1]. The plugin developer was contacted on September 3, 2025, and a fix was subsequently released [1].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
3News mentions
0No linked articles in our index yet.