# CVE-2024-2019: WP-DB-Table-Editor <= 1.8.4 - Missing Authorization to Authenticated(Contributor+) Database Access

> Authenticated contributors can modify database tables due to missing capability checks in the WP-DB-Table-Editor plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 4 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-75cp-x7c9-mcwq

## What is CVE-2024-2019?

CVE-2024-2019 is a high-severity missing authorization vulnerability in bobbysmith007 WP-DB-Table-Editor, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP-DB-Table-Editor plugin for WordPress is vulnerable to unauthorized access of data, modification of data, and loss of data due to lack of a default capability requirement on the 'dbte_render' function in all versions up to, and including, 1.8.4. This makes it possible for authenticated attackers, with contributor access and above, to modify database tables that the theme has been configured to use the plugin to edit.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-2019?


## How do I fix CVE-2024-2019?

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

## Is CVE-2024-2019 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2019 and fix it if it is affected.

What it is: CVE-2024-2019 is a high-severity missing authorization vulnerability in bobbysmith007 WP-DB-Table-Editor, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2019 in the wild and no public exploit code.

Affected product: bobbysmith007 WP-DB-Table-Editor. 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-2024-2019/ (Markdown: https://insights.sbomify.com/CVE-2024-2019/index.md)
```

## Sources

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

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