dbcve.org
Contact Form 7 Database AddonWordPress extension · Ciphercoin

CVE-2021-36886

HIGH · 8.8 CVSS v3.1 Published 2021-12-22
Fix available
A fix is available. Upgrade to 1.2.6.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability discovered in Contact Form 7 Database Addon – CFDB7 WordPress plugin (versions <= 1.2.5.9).

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the CFDB7 WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions, such as modifying plugin settings or deleting stored form data, by crafting malicious requests that the victim's browser automatically submits.

MitigationUpdate CFDB7 plugin to version greater than 1.2.5.9, which should include proper anti-CSRF token validation. If immediate update is not possible, disable the plugin until patched.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Contact Form 7 Database AddonWordPress extension
Affected:< 1.2.6.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

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

  1. Locate the CFDB7 plugin installation
    Check the WordPress wp-content/plugins directory for the cfdb7 or contact-form-7-database-addon folder, or query the WordPress database in the wp_options table for the option_name containing 'active_plugins' to verify if CFDB7 is listed as an active plugin.
    Affected if The CFDB7 plugin folder exists in the plugins directory and is registered in WordPress as an active plugin.
  2. Determine the installed CFDB7 plugin version
    Open the main plugin file (typically cfdb7.php or similar) in a text editor and locate the plugin header comment which contains the 'Version' field, or query the WordPress database for the option_name 'cfdb7_version' or 'plugin_options' if the version is stored there.
    Affected if The version string found is less than 1.2.6.1 (for example, 1.2.5.9 or earlier).
  3. Confirm the plugin handles form data
    Check the CFDB7 settings page in the WordPress admin dashboard under the 'Contact' or 'CFDB7' menu item, or inspect the database for tables created by the plugin (often named like wp_cfdb7_data or similar) to verify the plugin is storing or managing submitted form data.
    Affected if The plugin is configured to store form submissions from Contact Form 7, meaning any admin action to modify settings or delete form data via the plugin interface could be triggered via CSRF.
  4. Verify WordPress admin authentication is active
    In the WordPress admin dashboard, navigate to Users > All Users and confirm there is at least one user with the Administrator role, or query the wp_users and wp_usermeta tables to verify administrator-level users exist.
    Affected if There are authenticated administrators in the WordPress site who could be targeted by a CSRF attack through their logged-in session.

Your environment is affected if the CFDB7 plugin is installed, active, and running a version lower than 1.2.6.1, as this version lacks proper anti-CSRF token validation for admin actions.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.2.6.1 or later
Fixed in 1.2.6.1
Interim mitigation

Update CFDB7 plugin to version greater than 1.2.5.9, which should include proper anti-CSRF token validation. If immediate update is not possible, disable the plugin until patched.

Recommended fix High confidence

1.2.6.1

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Contact Form CFDB7' (or 'Contact Form 7 Database Addon') in the plugin list
  4. Click 'Update Now' to update the plugin to the latest version
  5. Alternatively, use WP-CLI: wp plugin update contact-form-cfdb7
  6. Verify the update was successful by checking the plugin version (should be 1.2.6.1 or later)
  7. Test that contact forms are submitting and storing data correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Contact Form 7 Database Addon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36886 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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