CVE-2025-7384

Database for Contact Form 7, WPforms, Elementor forms <= 1.4.3 - Unauthenticated PHP Object Injection to Arbitrary File Deletion

2025-08-12 00:00
mikemyers

Strategic Overview

Status
Patched in 1.4.4
Affected Version
<= 1.4.3
CVSS
9.8Critical
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2025-7384
View all Database for Contact Form 7, WPforms, Elementor forms vulnerabilities

At a glance

CVE-2025-7384 is a critical-severity Deserialization of Untrusted Data vulnerability in the Database for Contact Form 7, WPforms, Elementor forms WordPress plugin, affecting versions <= 1.4.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.4; sites on affected versions should update now. Disclosed August 2025, reported by mikemyers.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Reaching this weakness in Database for Contact Form 7, WPforms, Elementor forms <= 1.4.3 takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Database for Contact Form 7, WPforms, Elementor forms the fix is 1.4.4: builds <= 1.4.3 are affected, anything from 1.4.4 onward is not.

Remediation

Update to version 1.4.4, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Database for Contact Form 7, WPforms, Elementor forms 1.4.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C