dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-4665

CRITICAL · 9.6 CVSS v3.1 Published 2025-10-29
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

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
WordPress plugin Contact Form CFDB7 versions up to and including 1.3.2 are affected by a pre-authentication SQL injection vulnerability that cascades into insecure deserialization (PHP Object Injection). The weakness arises due to insufficient validation of user input in plugin endpoints, allowing crafted input to influence backend queries in unexpected ways. Using specially crafted payloads, this can escalate into unsafe deserialization, enabling arbitrary object injection in PHP. Although the issue is remotely exploitable without authentication, it does require a crafted interaction with the affected endpoint in order to trigger successfully.

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 confidence

The Contact Form CFDB7 WordPress plugin versions up to 1.3.2 contains a pre-authentication SQL injection vulnerability in insufficiently validated plugin endpoints. Crafted SQL injection payloads can trigger insecure PHP deserialization, leading to PHP Object Injection that can be leveraged for remote code execution.

MitigationUpdate the Contact Form CFDB7 plugin to the latest version beyond 1.3.2 immediately; if no patched version is available, disable the plugin and implement WAF rules to block SQL injection and deserialization patterns targeting the affected endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Check if CFDB7 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Contact Form CFDB7'. Alternatively, check for the existence of the /wp-content/plugins/contact-form-cfdb7/ directory on the filesystem.
    Affected if The Contact Form CFDB7 plugin is present in the WordPress installation
  2. Determine the installed version
    Open the main plugin file (usually cfdb7.php) in the plugin directory and locate the 'Version' header in the plugin comment block, or search for a version constant like 'define("CFDB7_VERSION", "...")'. Compare the version number to the affected range up to 1.3.2.
    Affected if The installed version is 1.3.2 or any earlier version
  3. Identify exposed plugin endpoints
    Review the plugin files for PHP files that handle form submissions directly (not through admin-ajax.php). Look for files that process $_GET, $_POST, or $_REQUEST parameters and pass them to database queries. Common paths include the plugin root directory and any 'includes' subfolder.
    Affected if The plugin exposes endpoints that accept user input without authentication (pre-authentication)
  4. Check for unserialize() usage on user input
    Search the plugin source code for calls to unserialize() function. Examine if any $_GET, $_POST, or $_REQUEST parameters are passed directly to unserialize() without validation. This is the mechanism that enables PHP Object Injection.
    Affected if User-controlled input from HTTP requests is passed to unserialize() without sanitization

The environment is affected if Contact Form CFDB7 plugin version 1.3.2 or lower is installed and the plugin exposes endpoints that accept unauthenticated input, particularly if unserialize() processes request parameters.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Contact Form CFDB7 plugin to the latest version beyond 1.3.2 immediately; if no patched version is available, disable the plugin and implement WAF rules to block SQL injection and deserialization patterns targeting the affected endpoints.

Recommended fix Moderate confidence

Contact Form CFDB7 version 1.3.3

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Contact Form CFDB7 plugin
  4. Check if an update is available and update to the latest version (1.3.3 or higher)
  5. Alternatively, download the latest version from wordpress.org or the plugin's official repository
  6. Deactivate and reinstall the plugin if automatic update does not work

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4665 — 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-4665 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