Missing AuthorizationWeakness · CWE-862

CVE-2026-4119

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-22

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The Create DB Tables plugin for WordPress is vulnerable to authorization bypass in all versions up to and including 1.2.1. The plugin registers admin_post action hooks for creating tables (admin_post_add_table) and deleting tables (admin_post_delete_db_table) without implementing any capability checks via current_user_can() or nonce verification via wp_verify_nonce()/check_admin_referer(). The admin_post hook only requires the user to be logged in, meaning any authenticated user including Subscribers can access these endpoints. The cdbt_delete_db_table() function takes a user-supplied table name from $_POST['db_table'] and executes a DROP TABLE SQL query, allowing any authenticated attacker to delete any database table including critical WordPress core tables such as wp_users or wp_options. The cdbt_create_new_table() function similarly allows creating arbitrary tables. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary database tables and delete any existing database table, potentially destroying the entire WordPress installation.

Technical summary

dbcve analysis · high confidence

The Create DB Tables WordPress plugin (versions up to 1.2.1) has an authorization bypass vulnerability. The admin_post action hooks for creating tables (admin_post_add_table) and deleting tables (admin_post_delete_db_table) lack capability checks via current_user_can() and nonce verification. Since admin_post only requires a logged-in user, any authenticated user including Subscriber-level can access these endpoints. The cdbt_delete_db_table() function directly uses the user-supplied $_POST['db_table'] value in DROP TABLE queries, allowing attackers to delete any database table including WordPress core tables like wp_users or wp_options.

MitigationImmediately remove or disable the plugin. If continued use is required, add proper capability checks (current_user_can('manage_options')) and nonce verification (wp_verify_nonce/check_admin_referer) to both admin_post hooks, plus sanitize and validate table name inputs before SQL execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Create DB Tables plugin is installed

Navigate to WordPress Admin > Plugins and look for 'Create DB Tables' plugin, or inspect the plugin directory /wp-content/plugins/ for a folder containing 'create-db-tables' or similar naming

Affected if The plugin is installed and active in WordPress
Identify the installed plugin version

Check the plugin's main PHP file (usually named create-db-tables.php or similar in the plugin folder) for the 'Version' header in the plugin comment block, or view the version in Plugins > Installed Plugins in WordPress admin

Affected if Version is 1.2.1 or any version up to 1.2.1 (no fixed version indicated)
Verify admin_post hooks lack capability checks

Inspect the plugin's main PHP file and search for 'admin_post_add_table' and 'admin_post_delete_db_table' hooks. Check if either hook has a call to current_user_can() before processing the request

Affected if The hooks are registered and do not call current_user_can() or equivalent capability checks
Confirm nonce verification is missing

Search the plugin code for wp_verify_nonce, check_admin_referer, or wp_nonce_field around the admin_post handlers. Look for nonce verification before database operations

Affected if No nonce verification is performed on the admin_post endpoints
Check if cdbt_delete_db_table uses unsanitized input

Locate the cdbt_delete_db_table function in the plugin code and examine if $_POST['db_table'] or similar user input is used directly in SQL queries without sanitization/validation

Affected if The function uses $_POST['db_table'] directly in DROP TABLE queries without prepare() or sanitization
Test endpoint accessibility with low-privilege user

As a Subscriber-level user (or any non-admin), attempt to access /wp-admin/admin-post.php?action=add_table or /wp-admin/admin-post.php?action=delete_db_table via curl or browser

Affected if The request is processed without a capability error or 403 redirect

If the Create DB Tables plugin version 1.2.1 or lower is installed and active, and the admin_post hooks lack current_user_can() checks and nonce verification, the site is affected by this authorization bypass allowing any logged-in user to delete arbitrary database tables.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Immediately remove or disable the plugin. If continued use is required, add proper capability checks (current_user_can('manage_options')) and nonce verification (wp_verify_nonce/check_admin_referer) to both admin_post hooks, plus sanitize and validate table name inputs before SQL execution.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-4119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4119 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-4119?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 9.1 Critical

Exploit likelihood EPSS, next 30 days 0.7%

Remediation

A high-priority fix

Have this fixed 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-4119 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References