dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22351

HIGH · 7.6 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 penguinarts Contact Form 7 Database – CFDB7 advanced-cf7-database allows SQL Injection.This issue affects Contact Form 7 Database – CFDB7: from n/a through <= 1.0.0.

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 7 Database plugin (CFDB7) allows attackers to inject malicious SQL commands via unsanitized user inputs. The vulnerability exists in the advanced-cf7-database component, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade to the latest version of the CFDB7 plugin which includes proper input sanitization and parameterized queries. If no patch is available, implement web application firewall rules to block SQL injection attack patterns until an update is released.

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

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

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 CFDB7 plugin is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins. Look for 'Contact Form 7 Database' or 'CFDB7' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list, indicating the vulnerable component is present in the environment.
  2. Identify installed CFDB7 version
    In WordPress admin panel, go to Plugins > Installed Plugins. Locate CFDB7 and note the version number displayed below the plugin name. Alternatively, check the plugin files in wp-content/plugins/contact-form-cfdb7/ for a version marker or readme.txt file.
    Affected if A version is returned and no patch has been applied to address the SQL injection vulnerability in the advanced-cf7-database component.
  3. Confirm advanced-cf7-database component is active
    Check the WordPress plugin settings page for CFDB7. Look for configuration options related to database storage, form submission handling, or any advanced database features. Review wp-config.php or plugin settings for database-related activity.
    Affected if The plugin is actively storing form submissions to the database, enabling the vulnerable code path for SQL injection.
  4. Review server logs for SQL injection indicators
    Examine web server access logs (typically in /var/log/apache2/, /var/log/nginx/, or cPanel access logs) for unusual SQL syntax patterns in URLs or POST data targeting forms that use CFDB7. Look for patterns like UNION SELECT, OR 1=1, or quotes followed by SQL keywords.
    Affected if Suspicious SQL syntax patterns appear in logs associated with form submission endpoints handled by CFDB7, indicating potential exploitation attempts.
  5. Audit database for unauthorized CFDB7 records
    Query the WordPress database (via phpMyAdmin or mysql CLI) for tables prefixed with wp_cf7_ or similar CFDB7 tables. Look for unexpected entries, particularly in form_data fields that may contain SQL commands or unusual encoded content.
    Affected if Database tables managed by CFDB7 contain unexpected data patterns or records that suggest injection attempts succeeded.

A user is affected if the CFDB7 plugin is installed and its database storage feature is active without having applied a security update that addresses the SQL injection in the advanced-cf7-database component.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of the CFDB7 plugin which includes proper input sanitization and parameterized queries. If no patch is available, implement web application firewall rules to block SQL injection attack patterns until an update is released.

Have this fixed 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 help mitigating

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-2025-22351 — 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-2025-22351 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