WP-DB-Table-Editor <= 1.8.4 - Missing Authorization to Authenticated(Contributor+) Database Access
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WP-DB-Table-Editor
- Affected Version
<= 1.8.4- CVSS
- 7.5High
- Weakness type
- CWE-284 · Improper Access Control
- CVE
CVE-2024-2019
At a glance
CVE-2024-2019 is a high-severity Improper Access Control vulnerability in the WP-DB-Table-Editor WordPress plugin, affecting versions <= 1.8.4. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2024, reported by Francesco Carlucci.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-284: Improper Access Control
WP-DB-Table-Editor <= 1.8.4 carries this weakness at dbte_render, and reaching it takes an account at Contributor level or above. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.
Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. No fixed build of this plugin is recorded for WP-DB-Table-Editor yet, so installs running <= 1.8.4 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C