CVE-2026-4031: CWE-862 Missing Authorization in wpengine Database Backup for WordPress
The Database Backup for WordPress plugin by wpengine has an authorization bypass vulnerability in versions up to 2. 5. 2. This flaw allows unauthenticated attackers to manipulate the backup directory parameter, causing scheduled backups to be written to publicly accessible locations. Attackers can then intercept backup files containing sensitive information such as database credentials and user password hashes. Exploitation depends on scheduled backups being configured by the site administrator. No official patch or remediation guidance is currently provided.
AI Analysis
Technical Summary
CVE-2026-4031 is an authorization bypass vulnerability (CWE-862) in the Database Backup for WordPress plugin by wpengine, affecting all versions up to 2.5.2. The vulnerability arises because the plugin does not restrict access to the wp_db_temp_dir parameter, which controls the directory where database backups are stored. An unauthenticated attacker can send a specially crafted request to wp-cron.php with a manipulated wp_db_temp_dir value pointing to a publicly accessible directory. If a scheduled backup runs, the backup file is saved in this location with a predictable filename, allowing the attacker to retrieve sensitive data including database credentials, password hashes, and personally identifiable information. Exploitation requires that scheduled backups are enabled by the site administrator. There is no vendor advisory or patch available at this time.
Potential Impact
Successful exploitation leads to sensitive information exposure, including database credentials, user password hashes, and personally identifiable information. This can compromise the confidentiality of the affected WordPress site’s data. The vulnerability does not affect integrity or availability directly. Exploitation requires no privileges and no user interaction, making it a high-severity risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should consider disabling scheduled backups or restricting access to wp-cron.php and the wp_db_temp_dir parameter to trusted users only. Monitoring for unusual requests to wp-cron.php may help detect exploitation attempts.
CVE-2026-4031: CWE-862 Missing Authorization in wpengine Database Backup for WordPress
Description
The Database Backup for WordPress plugin by wpengine has an authorization bypass vulnerability in versions up to 2. 5. 2. This flaw allows unauthenticated attackers to manipulate the backup directory parameter, causing scheduled backups to be written to publicly accessible locations. Attackers can then intercept backup files containing sensitive information such as database credentials and user password hashes. Exploitation depends on scheduled backups being configured by the site administrator. No official patch or remediation guidance is currently provided.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4031 is an authorization bypass vulnerability (CWE-862) in the Database Backup for WordPress plugin by wpengine, affecting all versions up to 2.5.2. The vulnerability arises because the plugin does not restrict access to the wp_db_temp_dir parameter, which controls the directory where database backups are stored. An unauthenticated attacker can send a specially crafted request to wp-cron.php with a manipulated wp_db_temp_dir value pointing to a publicly accessible directory. If a scheduled backup runs, the backup file is saved in this location with a predictable filename, allowing the attacker to retrieve sensitive data including database credentials, password hashes, and personally identifiable information. Exploitation requires that scheduled backups are enabled by the site administrator. There is no vendor advisory or patch available at this time.
Potential Impact
Successful exploitation leads to sensitive information exposure, including database credentials, user password hashes, and personally identifiable information. This can compromise the confidentiality of the affected WordPress site’s data. The vulnerability does not affect integrity or availability directly. Exploitation requires no privileges and no user interaction, making it a high-severity risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should consider disabling scheduled backups or restricting access to wp-cron.php and the wp_db_temp_dir parameter to trusted users only. Monitoring for unusual requests to wp-cron.php may help detect exploitation attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-12T00:34:09.270Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a05c8f4ec166c07b0dcb7a5
Added to database: 5/14/2026, 1:07:00 PM
Last enriched: 5/14/2026, 1:21:35 PM
Last updated: 5/14/2026, 5:19:19 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.