HomeWordPress vulnerabilitiesWP-DBManager
WP-DBManager vulnerabilities
WP-DBManager has 4 known vulnerabilities in this database. The most recent published record is dated 15 Aug 2022.
- Known vulnerabilities
- 4
- Active installs
- 60,000+
- Latest version
- 4.0.0
- Last updated
- 9 Aug 2026
- Most recent
- 15 Aug 2022
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-2022-2354 | High 7.2 | Before 2.80.8 | Fixed in 2.80.8 | 15 Aug 2022 |
| Security weakness CVE-2014-8335 | High 7.8 | Up to 2.7.1 | Fixed in a later version (latest 4.0.0) | 5 Jan 2018 |
| Security weakness CVE-2014-8336 | Medium 6.5 | Up to 2.7.1 | Fixed in a later version (latest 4.0.0) | 5 Jan 2018 |
| Remote code execution CVE-2014-8334 | Not scored | Up to 2.71 | Fixed in a later version (latest 4.0.0) | 31 Oct 2014 |
Read the published descriptions
- CVE-2022-2354, 15 Aug 2022
- The WP-DBManager WordPress plugin before 2.80.8 does not prevent administrators from running arbitrary commands on the server in multisite installations, where only super-administrators should. CVE record
- CVE-2014-8335, 5 Jan 2018
- (1) wp-dbmanager.php and (2) database-manage.php in the WP-DBManager (aka Database Manager) plugin before 2.7.2 for WordPress place credentials on the mysqldump command line, which allows local users to obtain sensitive information by listing the process. CVE record
- CVE-2014-8336, 5 Jan 2018
- The "Sql Run Query" panel in WP-DBManager (aka Database Manager) plugin before 2.7.2 for WordPress allows remote attackers to read arbitrary files by leveraging failure to sufficiently limit queries, as demonstrated by use of LOAD_FILE in an INSERT statement. CVE record
- CVE-2014-8334, 31 Oct 2014
- The WP-DBManager (aka Database Manager) plugin before 2.7.2 for WordPress allows remote authenticated users to execute arbitrary commands via shell metacharacters in the (1) $backup['filepath'] (aka "Path to Backup:" field) or (2) $backup['mysqldumppath'] variable. CVE record
What to do if you run WP-DBManager
If you run WP-DBManager, 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-DBManager vulnerabilities
Free. We email you when a new vulnerability is published for WP-DBManager, 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.