CVE-2020-7048 in the critical feed json
The WordPress plugin, WP Database Reset through 3.1, contains a flaw that allowed any unauthenticated user to reset any table in the databa…
published 6y ago modified 4mo ago also EUVD-2020-28182
- cvss
- 9.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 22.9%
- EPSS 22.9% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2020-7048 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
22.93% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wordfence.com https://www.wordfence.com/blog/2020/01/easily-exploitable-vulnerabilities-patched-in-wp-database-reset-plugin/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.1 | CVSS:3.0/AC:L/AV:N/A:H/C:N/I:H/PR:N/S:U/UI:N |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| CNA | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
- Technology feeds
References
-
wordfence.com
/blog/2020/01/easily-exploitable-vulnerabilities-patched-in-wp-database-reset-plugin/
exploit, patch, third-party-advisory
-
wordpress.org
/plugins/wordpress-database-reset/#developers
release-notes, third-party-advisory
-
wpvulndb.com
/vulnerabilities/10027
third-party-advisory
Sources
- CVE List CVE-2020-7048
- NVD CVE-2020-7048
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.