dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-7384

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-13
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 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
The Database for Contact Form 7, WPforms, Elementor forms plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.4.3 via deserialization of untrusted input in the get_lead_detail function. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain in the Contact Form 7 plugin, which is likely to be used alongside, allows attackers to delete arbitrary files, leading to a denial of service or remote code execution when the wp-config.php file is deleted.

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

This WordPress form database plugin contains a PHP Object Injection vulnerability in the get_lead_detail function (versions up to 1.4.3) due to unsafe deserialization of untrusted input. Unauthenticated attackers can inject PHP objects, and when chained with a POP chain in the Contact Form 7 plugin, can delete arbitrary files including wp-config.php, leading to DoS or RCE.

MitigationUpdate the plugin to version 1.4.4 or later. Also ensure Contact Form 7 is updated to address the POP chain that enables file deletion and RCE.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the form database plugin
    In WordPress admin, go to Plugins and look for any plugin that stores form data to a database. Common names include 'Contact Form to Database' or similar. Note the exact plugin name and developer.
    Affected if The plugin named is installed and matches the vulnerable software
  2. Check the plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Find the form database plugin and compare the version number against '1.4.3' (versions 1.4.3 and below are vulnerable).
    Affected if The installed version is 1.4.3 or lower
  3. Confirm Contact Form 7 is installed
    In WordPress admin, go to Plugins and verify if the Contact Form 7 plugin is installed. This plugin is required for the POP chain exploit to achieve file deletion.
    Affected if Contact Form 7 is installed and provides the POP chain
  4. Check if the vulnerable endpoint is accessible
    Probe the URL pattern /?action=get_lead_detail or similar AJAX endpoints exposed by the plugin. These endpoints handle the vulnerable unserialize() call.
    Affected if The endpoint responds and processes untrusted input without validation

You are affected if the form database plugin is installed at version 1.4.3 or lower AND Contact Form 7 is present, enabling the full exploitation chain for arbitrary file deletion.

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 plugin to version 1.4.4 or later. Also ensure Contact Form 7 is updated to address the POP chain that enables file deletion and RCE.

Recommended fix High confidence

Version 1.4.4 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Database for Contact Form 7, WPforms, Elementor forms' plugin
  4. Click 'Update Now' to install the latest version
  5. Alternatively, navigate to Dashboard > Updates and update all plugins
  6. Verify the updated version is greater than 1.4.3 after update completes

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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