CVE-2025-4665: Pre-auth SQL Injection in WordPress Contact Form CFDB7
CVE-2025-4665 is a critical pre-authentication SQL injection vulnerability affecting the WordPress plugin Contact Form CFDB7 up to and including version 1.3.2. According to the provided content, the flaw is caused by insufficient validation of user-supplied input in one or more plugin endpoints, allowing crafted requests to manipulate backend SQL queries. The content further states that this SQL injection condition can cascade into insecure deserialization, resulting in PHP Object Injection when attacker-controlled data is later processed unsafely. In environments where a suitable gadget chain exists, this secondary condition may enable remote code execution.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can allow an unauthenticated remote attacker to read and modify database contents associated with the affected WordPress site. Based on the provided content, the SQL injection may also lead to insecure deserialization and PHP Object Injection, which can further expand impact to arbitrary object injection and potentially remote code execution if the surrounding WordPress or plugin environment contains usable gadget chains. The provided content also indicates high impact to confidentiality, integrity, and availability.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by disabling the Contact Form CFDB7 plugin or any unnecessary plugin features until an update can be applied. Restrict access to vulnerable endpoints where operationally feasible, monitor for suspicious requests targeting CFDB7 endpoints, and review database and application logs for indicators of SQL injection attempts. Because the content indicates possible deserialization follow-on risk, minimize or remove unsafe PHP deserialization of untrusted data in the hosting environment where possible.
Remediation
Patch, then assume compromise.
Update Contact Form CFDB7 to version 1.3.3 or later, as the provided content identifies that release line as the recommended fix. Apply vendor-provided security patches immediately across all affected WordPress installations. Where code-level remediation is relevant, the underlying issue should be addressed by enforcing strict server-side input validation and using parameterized queries or prepared statements for all database interactions, and by eliminating unsafe unserialize paths for attacker-influenced data.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2025-4665 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2025-4665 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-4665?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-4665.
- Is there a patch for CVE-2025-4665?
- Update Contact Form CFDB7 to version 1.3.3 or later, as the provided content identifies that release line as the recommended fix. Apply vendor-provided security patches immediately across all affected WordPress installations.
- How severe is CVE-2025-4665?
- CVE-2025-4665 has a CVSS v3.1 score of 9.6 (Critical) and an EPSS score of 0.33% (26th percentile) as of Sep 25, 2026.
Recent activity
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.