# CVE-2020-7047: Privilege escalation in n/a

> Authenticated users with minimal permissions can escalate to administrator and delete all other users via a specific request in the WP Database Reset plugin.

- **Severity:** Critical 9.9 (`CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9f6m-8x44-j5mr

## What is CVE-2020-7047?

CVE-2020-7047 is a critical vulnerability in n/a, published on 16 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2020-7047?

It affects 1 product.


Products: Webfactoryltd Wp Database Reset.

## How do I fix CVE-2020-7047?

No fix has been published for CVE-2020-7047 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-7047 being exploited?

There is no known exploitation of CVE-2020-7047 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-7048](https://insights.sbomify.com/CVE-2020-7048/): Missing authorization in n/a (critical 9.1)
- [CVE-2024-1501](https://insights.sbomify.com/CVE-2024-1501/): Database Reset <= 3.22 - Cross-Site Request Forgery to WP Reset Plugin Installation (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7047 and fix it if it is affected.

What it is: CVE-2020-7047 is a critical vulnerability in n/a, published on 16 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7047 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-7047/ (Markdown: https://insights.sbomify.com/CVE-2020-7047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7047
- OSV: https://osv.dev/vulnerability/CVE-2020-7047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-7047/
Summaries are generated and may contain mistakes; the official description above is the record.