CVE-2026-12094
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.
NVD · uneditedThe Advanced Contact Form 7 - Compact DB plugin for WordPress is vulnerable to unauthorized deletion of data due to a missing capability check on the cf7cdb_ajax_delete_user() function in versions up to, and including, 1.0.0. The handler is registered against both `wp_ajax_cf7cdb_delete` and `wp_ajax_nopriv_cf7cdb_delete`, and it performs no nonce verification, no capability check, and no ownership check before invoking `$wpdb->delete()` against the `wp_cf7cdb_data` table with an attacker-supplied integer ID. This makes it possible for unauthenticated attackers to delete arbitrary contact form submission entries stored by the plugin by iterating sequential primary-key IDs.
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.
dbcve analysis · high confidenceThe Advanced Contact Form 7 - Compact DB WordPress plugin versions up to 1.0.0 lacks authorization, capability checks, and nonce verification on the cf7cdb_ajax_delete_user() AJAX handler. The function is exposed to both authenticated and unauthenticated users via wp_ajax_cf7cdb_delete and wp_ajax_nopriv_cf7cdb_delete hooks, allowing any visitor to delete arbitrary database records by supplying sequential integer IDs to $wpdb->delete().
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Advanced Contact Form 7 - Compact DB plugin is installedCheck the WordPress plugins directory or use wp-cli: wp plugin list --search='*compact*db*' or inspect /wp-content/plugins/ for a folder named cf7-compact-db or similarAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionRead the plugin header from main plugin file (usually in wp-content/plugins/[plugin-folder]/index.php or cf7cdb.php) and look for the Version: field in the plugin comments, or query the wp_options table for the option_name containing the plugin versionAffected if The version is 1.0.0 or lower (all versions up to 1.0.0 are affected)
-
Check if unauthenticated AJAX endpoint is registeredSearch plugin PHP files for 'wp_ajax_nopriv_cf7cdb_delete' string, or inspect the site's AJAX handler by making a GET request to /wp-admin/admin-ajax.php?action=cf7cdb_delete (no auth) and observe the responseAffected if The hook 'wp_ajax_nopriv_cf7cdb_delete' is registered, meaning unauthenticated users can trigger the delete function
-
Verify the vulnerable function lacks authorization checksLocate the cf7cdb_ajax_delete_user() function in the plugin code and inspect whether it calls current_user_can(), checks a nonce, or validates ownership before executing $wpdb->delete()Affected if The function executes $wpdb->delete() without capability checks, nonce verification, or ownership validation
You are affected if the plugin is installed with version 1.0.0 or lower and the unauthenticated AJAX hook (wp_ajax_nopriv_cf7cdb_delete) is active, allowing any visitor to delete database records without authorization.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataAdd nonce verification, capability checks (e.g., current_user_can('manage_options')), and ownership validation to ensure the current user owns or has rights to delete the specific contact form submission before executing $wpdb->delete().
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12094 in production — separate from our analysis above.
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.
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.
- 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