HomeWordPress vulnerabilitiesBackWPup
BackWPup vulnerabilities
BackWPup has 12 known vulnerabilities in this database. The most recent published record is dated 11 Sep 2026.
- Known vulnerabilities
- 12
- Active installs
- 400,000+
- Latest version
- 5.7.6
- Last updated
- 7 Sep 2026
- Most recent
- 11 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-86815 | Medium 5.5 | Before 5.7.5 | Fixed in 5.7.5 | 11 Sep 2026 |
| Remote code execution CVE-2026-6227 | High 7.2 | Up to 5.6.6 | Fixed in a later version (latest 5.7.6) | 14 Apr 2026 |
| Privilege escalation CVE-2025-15041 | High 7.2 | Up to 5.6.2 | Fixed in a later version (latest 5.7.6) | 19 Feb 2026 |
| Broken access control CVE-2025-10579 | Medium 5.3 | Up to 5.5.0 | Fixed in a later version (latest 5.7.6) | 25 Oct 2025 |
| Path traversal CVE-2023-5505 | Medium 6.8 | Before 4.0.2 | Fixed in 4.0.2 | 17 Aug 2024 |
| Security weakness CVE-2023-7164 | High 7.5 | Before 4.0.4 | Fixed in 4.0.4 | 8 Apr 2024 |
| Security weakness CVE-2023-5775 | Low 2.2 | Before 4.0.3 | Fixed in 4.0.3 | 26 Feb 2024 |
| Path traversal CVE-2023-5504 | High 8.7 | Up to 4.0.1 | Fixed in a later version (latest 5.7.6) | 11 Jan 2024 |
| Security weakness CVE-2017-2551 | High 7.5 | Up to 3.4.1 | Fixed in a later version (latest 5.7.6) | 28 Sep 2017 |
| Cross-site scripting (XSS) CVE-2013-4626 | Not scored | Up to 3.0.12 | Fixed in a later version (latest 5.7.6) | 26 Sep 2013 |
| Path traversal CVE-2011-5208 | Not scored | Up to 1.4.0 | Fixed in a later version (latest 5.7.6) | 8 Oct 2012 |
| File inclusion CVE-2011-4342 | Not scored | Up to 1.7.1 | Fixed in a later version (latest 5.7.6) | 8 Oct 2012 |
Read the published descriptions
- CVE-2026-86815, 11 Sep 2026
- The BackWPup WordPress plugin before 5.7.5 does not properly restrict access to several of its REST API routes for job, backup-destination, and backup-execution management, allowing users holding a BackWPup WordPress plugin before 5.7.5-defined, administrator-assigned limited role to create and run backup jobs and exfiltrate a full database backup to an attacker-controlled destination. CVE record
- CVE-2026-6227, 14 Apr 2026
- The BackWPup plugin for WordPress is vulnerable to Local File Inclusion via the `block_name` parameter of the `/wp-json/backwpup/v1/getblock` REST endpoint in all versions up to, and including, 5.6.6 due to a non-recursive `str_replace()` sanitization of path traversal sequences. This makes it possible for authenticated attackers, with Administrator-level access and above, to include arbitrary PHP files on the server via crafted traversal sequences (e.g., `....//`), which can be leveraged to read sensitive files such as `wp-config.php` or achieve remote code execution in certain configurations. Administrators have the ability to grant individual users permission to handle backups, which may then allow lower-level users to exploit this vulnerability. CVE record
- CVE-2025-15041, 19 Feb 2026
- The BackWPup - WordPress Backup & Restore Plugin plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the save_site_option() function in all versions up to, and including, 5.6.2. This makes it possible for authenticated attackers, with level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site. CVE record
- CVE-2025-10579, 25 Oct 2025
- 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). CVE record
- CVE-2023-5505, 17 Aug 2024
- The BackWPup plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 4.0.1 via the job-specific backup folder. This allows authenticated attackers to store backups in arbitrary folders on the server provided they can be written to by the server. Additionally, default settings will place an index.php and a .htaccess file into the chosen directory (unless already present) when the first backup job is run that are intended to prevent directory listing and file access. This means that an attacker could set the backup directory to the root of another site in a shared environment and thus disable that site. CVE record
- CVE-2023-7164, 8 Apr 2024
- The BackWPup WordPress plugin before 4.0.4 does not prevent Directory Listing in its temporary backup folder, allowing unauthenticated attackers to download backups of a site's database. CVE record
- CVE-2023-5775, 26 Feb 2024
- The BackWPup plugin for WordPress is vulnerable to Plaintext Storage of Backup Destination Password in all versions up to, and including, 4.0.2. This is due to to the plugin improperly storing backup destination passwords in plaintext. This makes it possible for authenticated attackers, with administrator-level access, to retrieve the password from the password input field in the UI or from the options table where the password is stored. CVE record
- CVE-2023-5504, 11 Jan 2024
- The BackWPup plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 4.0.1 via the Log File Folder. This allows authenticated attackers to store backups in arbitrary folders on the server provided they can be written to by the server. Additionally, default settings will place an index.php and a .htaccess file into the chosen directory (unless already present) when the first backup job is run that are intended to prevent directory listing and file access. This means that an attacker could set the backup directory to the root of another site in a shared environment and thus disable that site. CVE record
- CVE-2017-2551, 28 Sep 2017
- Vulnerability in Wordpress plugin BackWPup before v3.4.2 allows possible brute forcing of backup file for download. CVE record
- CVE-2013-4626, 26 Sep 2013
- Cross-site scripting (XSS) vulnerability in the BackWPup plugin before 3.0.13 for WordPress allows remote attackers to inject arbitrary web script or HTML via the tab parameter to wp-admin/admin.php. CVE record
- CVE-2011-5208, 8 Oct 2012
- Multiple directory traversal vulnerabilities in the BackWPup plugin before 1.4.1 for WordPress allow remote attackers to read arbitrary files via a .. (dot dot) in the wpabs parameter to (1) app/options-view_log-iframe.php or (2) app/options-runnow-iframe.php. CVE record
- CVE-2011-4342, 8 Oct 2012
- PHP remote file inclusion vulnerability in wp_xml_export.php in the BackWPup plugin before 1.7.2 for WordPress allows remote attackers to execute arbitrary PHP code via a URL in the wpabs parameter. CVE record
What to do if you run BackWPup
If you run BackWPup, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new BackWPup vulnerabilities
Free. We email you when a new vulnerability is published for BackWPup, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.