HomeWordPress vulnerabilitiesWP Database Backup
WP Database Backup vulnerabilities
WP Database Backup has 10 known vulnerabilities in this database. The most recent published record is dated 2 Jul 2026.
- Known vulnerabilities
- 10
- Active installs
- 20,000+
- Latest version
- 7.13
- Last updated
- 24 Aug 2026
- Most recent
- 2 Jul 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 |
|---|---|---|---|---|
| Remote code execution CVE-2026-9834 | High 7.2 | Up to 7.11 | Fixed in a later version (latest 7.13) | 2 Jul 2026 |
| Remote code execution CVE-2019-25224 | Critical 9.8 | Before 5.2 | Fixed in 5.2 | 25 Jul 2025 |
| Sensitive data exposure CVE-2024-12330 | High 7.5 | Up to 7.3 | Fixed in a later version (latest 7.13) | 9 Jan 2025 |
| Cross-site scripting (XSS) CVE-2022-2271 | Medium 4.8 | Before 5.9 | Fixed in 5.9 | 5 Sep 2022 |
| Security weakness CVE-2020-7241 | High 7.5 | Up to 5.5 | Fixed in a later version (latest 7.13) | 20 Jan 2020 |
| Cross-site scripting (XSS) CVE-2019-14949 | Medium 6.1 | Before 5.1.2 | Fixed in 5.1.2 | 12 Aug 2019 |
| Cross-site scripting (XSS) CVE-2016-10873 | Medium 6.1 | Before 4.3.3 | Fixed in 4.3.3 | 12 Aug 2019 |
| Cross-site request forgery (CSRF) CVE-2016-10874 | High 8.8 | Before 4.3.3 | Fixed in 4.3.3 | 12 Aug 2019 |
| Cross-site scripting (XSS) CVE-2016-10875 | Medium 6.1 | Before 4.3.1 | Fixed in 4.3.1 | 12 Aug 2019 |
| Cross-site request forgery (CSRF) CVE-2016-10876 | High 8.8 | Before 4.3.1 | Fixed in 4.3.1 | 12 Aug 2019 |
Read the published descriptions
- CVE-2026-9834, 2 Jul 2026
- The WP Database Backup - Unlimited Database & Files Backup by Backup for WP plugin for WordPress is vulnerable to OS Command Injection in all versions up to and including 7.11 via the `wp_db_exclude_table` parameter. This is due to the direct concatenation of user-supplied `$_POST['wp_db_exclude_table']` values into the `mysqldump` shell command string in the `mysqldump()` function of `includes/admin/class-wpdb-admin.php` without wrapping them in `escapeshellarg()`-every other argument in the same command (DB_USER, DB_PASSWORD, host, filename, DB_NAME) is properly escaped, making the exclude-table values the sole exception-and because the only applied filtering, `sanitize_text_field()` via `recursive_sanitize_text_field()`, strips HTML tags but leaves shell metacharacters such as `;`, `|`, `` ` ``, and `$()` intact. This makes it possible for authenticated attackers, with administrator-level access and above, to execute arbitrary operating system commands on the server, potentially enabling full remote code execution. The injection is stored: malicious values submitted through the plugin settings form are persisted to the WordPress options table via `update_option('wp_db_exclude_table')` and later retrieved with `get_option()` and passed unsanitized to `shell_exec()` whenever a backup operation runs. CVE record
- CVE-2019-25224, 25 Jul 2025
- The WP Database Backup plugin for WordPress is vulnerable to OS Command Injection in versions before 5.2 via the mysqldump function. This vulnerability allows unauthenticated attackers to execute arbitrary commands on the host operating system. CVE record
- CVE-2024-12330, 9 Jan 2025
- The WP Database Backup - Unlimited Database & Files Backup by Backup for WP plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 7.3 via publicly accessible back-up files. This makes it possible for unauthenticated attackers to extract sensitive data including all information stored in the database. CVE record
- CVE-2022-2271, 5 Sep 2022
- The WP Database Backup WordPress plugin before 5.9 does not escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2020-7241, 20 Jan 2020
- The WP Database Backup plugin through 5.5 for WordPress stores downloads by default locally in the directory wp-content/uploads/db-backup/. This might allow attackers to read ZIP archives by guessing random ID numbers, guessing date strings with a 2020_{0..1}{0..2}_{0..3}{0..9} format, guessing UNIX timestamps, and making HTTPS requests with the complete guessed URL. CVE record
- CVE-2019-14949, 12 Aug 2019
- The wp-database-backup plugin before 5.1.2 for WordPress has XSS. CVE record
- CVE-2016-10873, 12 Aug 2019
- The wp-database-backup plugin before 4.3.3 for WordPress has XSS. CVE record
- CVE-2016-10874, 12 Aug 2019
- The wp-database-backup plugin before 4.3.3 for WordPress has CSRF. CVE record
- CVE-2016-10875, 12 Aug 2019
- The wp-database-backup plugin before 4.3.1 for WordPress has XSS. CVE record
- CVE-2016-10876, 12 Aug 2019
- The wp-database-backup plugin before 4.3.1 for WordPress has CSRF. CVE record
What to do if you run WP Database Backup
If you run WP Database Backup, 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 WP Database Backup vulnerabilities
Free. We email you when a new vulnerability is published for WP Database Backup, 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.