dbcve.org
Contact Form To DbWordPress extension · Bestwebsoft

CVE-2024-35678

HIGH · 8.8 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 1.7.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in BestWebSoft Contact Form to DB by BestWebSoft.This issue affects Contact Form to DB by BestWebSoft: from n/a through 1.7.2.

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

SQL injection vulnerability in the Contact Form to DB plugin allows attackers to inject malicious SQL commands through form inputs that are not properly sanitized before being used in database queries. This could allow unauthorized database access, data exfiltration, or manipulation of stored data.

MitigationUpdate the Contact Form to DB plugin to the latest patched version. If no patch is available, disable the plugin until a fix is released. Implement input validation and parameterized queries as a temporary mitigation.

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 To DbWordPress extension
Affected:< 1.7.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify Contact Form to DB plugin is installed
    Locate the plugin directory in the WordPress plugins folder (typically /wp-content/plugins/contact-form-to-db or similar). Check for the presence of the plugin files.
    Affected if The plugin directory exists on the server
  2. Check installed plugin version
    Open the main plugin file (usually index.php or the primary PHP file in the plugin directory) and locate the plugin header comment which contains the Version field. Alternatively, check the WordPress admin plugins page for the installed version.
    Affected if The installed version is lower than 1.7.3
  3. Confirm plugin is active
    Check the WordPress database wp_options table for the active_plugins option, or log into the WordPress admin panel and verify the plugin status in the Plugins list.
    Affected if The plugin appears in the list of active plugins
  4. Check for form submissions
    Inspect the plugin database tables (typically created by the plugin to store form submissions) to see if any form data exists. Use: SELECT * FROM wp_cfdb7_or_similar_table_name LIMIT 10;
    Affected if Form submission data exists in the database, indicating the plugin is processing user input
  5. Review database query logs
    Check database logs or enable query logging to look for suspicious SQL patterns in form submission data. Look for SQL keywords (UNION, SELECT, INSERT, DROP) within form field values.
    Affected if Unusual SQL syntax appears in form submission records or database logs

The environment is affected if the Bestwebsoft Contact Form To Db plugin is installed, active, and running at a version lower than 1.7.3, with form submissions being processed.

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.7.3 or later
Fixed in 1.7.3
Interim mitigation

Update the Contact Form to DB plugin to the latest patched version. If no patch is available, disable the plugin until a fix is released. Implement input validation and parameterized queries as a temporary mitigation.

Recommended fix High confidence

1.7.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Contact Form to DB' (or 'Contact Form To Db') by BestWebSoft
  4. Click 'Update now' if an update is available, or click 'Deactivate' then 'Delete' and install version 1.7.3 from the WordPress plugin repository
  5. Verify the plugin is running version 1.7.3 after the update

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

Fix this in Contact Form To Db 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-2024-35678 — 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-2024-35678 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