CVE-2026-4031
HighSummary
The Database Backup plugin for WordPress is vulnerable to authorization bypass in all versions up to and including 2.5.2. The issue arises from the plugin not restricting access to the wp_db_temp_dir parameter, allowing unauthenticated attackers to intercept backup files.
Risk Assessment
Attackers can gain access to sensitive information, including database credentials, user password hashes, and personally identifiable information. This requires the site administrator to have configured scheduled backups.
Recommendation
It is recommended to update the plugin to the latest version and implement additional security measures to restrict access to configuration parameters. Consider changing the backup storage location to a more secure one.
Other vulnerabilities in Database Backup for WordPress plugin
Original NVD description (English source)
The Database Backup for WordPress plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.5.2. This is due to the plugin not restricting access to the wp_db_temp_dir parameter, which controls where database backups are written. This makes it possible for unauthenticated attackers to send a request to wp-cron.php with a poisoned wp_db_temp_dir value pointing to a publicly accessible directory (e.g., wp-content/uploads/), and if a scheduled backup is due, intercept the backup file before it is cleaned up. The backup file has a predictable name based on the database name, table prefix, date, and Swatch Internet Time, making interception reliable. Successful exploitation leads to Sensitive Information Exposure including database credentials, user password hashes, and personally identifiable information. This vulnerability requires that the site administrator has configured scheduled backups.