HomeWordPress vulnerabilitiesDatabase Reset
Database Reset vulnerabilities
Database Reset has 3 known vulnerabilities in this database. The most recent published record is dated 21 Feb 2024.
- Known vulnerabilities
- 3
- Active installs
- 10,000+
- Latest version
- 3.25
- Last updated
- 16 Aug 2026
- Most recent
- 21 Feb 2024
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 |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2024-1501 | Medium 4.7 | Before 3.23 | Fixed in 3.23 | 21 Feb 2024 |
| Privilege escalation CVE-2020-7047 | High 8.8 | Up to 3.1 | Fixed in a later version (latest 3.25) | 16 Jan 2020 |
| Authentication bypass CVE-2020-7048 | Critical 9.1 | Up to 3.1 | Fixed in a later version (latest 3.25) | 16 Jan 2020 |
Read the published descriptions
- CVE-2024-1501, 21 Feb 2024
- The Database Reset plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.22. This is due to missing or incorrect nonce validation on the install_wpr() function. This makes it possible for unauthenticated attackers to install the WP Reset Plugin via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2020-7047, 16 Jan 2020
- The WordPress plugin, WP Database Reset through 3.1, contains a flaw that gave any authenticated user, with minimal permissions, the ability (with a simple wp-admin/admin.php?db-reset-tables[]=users request) to escalate their privileges to administrator while dropping all other users from the table. CVE record
- CVE-2020-7048, 16 Jan 2020
- The WordPress plugin, WP Database Reset through 3.1, contains a flaw that allowed any unauthenticated user to reset any table in the database to the initial WordPress set-up state (deleting all site content stored in that table), as demonstrated by a wp-admin/admin-post.php?db-reset-tables[]=comments URI. CVE record
What to do if you run Database Reset
If you run Database Reset, 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 Database Reset vulnerabilities
Free. We email you when a new vulnerability is published for Database Reset, 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.