Is wp-database-backup (WordPress plugin) vulnerable?

WordPress wp-database-backup has 8 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

8advisories
1critical
0on CISA KEV
1no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-25224The WP Database Backup plugin for WordPress is vulnerable to OS Command Injection in versions before 5.2 via the mysqldump function. This vucritical9.8<5.25.2
CVE-2020-7241The WP Database Backup plugin through 5.5 for WordPress stores downloads by default locally in the directory wp-content/uploads/db-backup/. high7.5<=5.5–
CVE-2019-14949The wp-database-backup plugin before 5.1.2 for WordPress has XSS.medium6.1<5.1.25.1.2
CVE-2016-10873The wp-database-backup plugin before 4.3.3 for WordPress has XSS.medium6.1<4.3.34.3.3
CVE-2016-10875The wp-database-backup plugin before 4.3.1 for WordPress has XSS.medium6.1<4.3.14.3.1
CVE-2016-10876The wp-database-backup plugin before 4.3.1 for WordPress has CSRF.high8.8<4.3.14.3.1
CVE-2016-10874The wp-database-backup plugin before 4.3.3 for WordPress has CSRF.high8.8<4.3.34.3.3
CVE-2022-2271The WP Database Backup WordPress plugin before 5.9 does not escape some of its settings, which could allow high privilege users such as admimedium4.8<5.95.9

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.