Skip to main content
VulnerabilityPublished

CVE-2025-4665: CFDB7 (WordPress plugin) · SQL Injection

Affects CFDB7 (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.6 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WordPress Contact Form 7 Database Addon CFDB7 By Arshid CFDB7Affected
  • =0.0.0
Fixed in–

AI-suggested

  1. Immediately identify and inventory all WordPress installations using the Contact Form 7 Database Addon CFDB7 plugin, especially versions up to 1.3.2.
  2. Apply any available official patches or updates from the plugin vendor as soon as they are released.
  3. Implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts targeting the plugin’s endpoints, focusing on suspicious payloads and unusual POST requests to contact form submission URLs.
  4. Conduct thorough security audits and code reviews of customizations involving the plugin to ensure no additional vulnerabilities exist.
  5. Monitor web server and application logs for anomalous activity indicative of exploitation attempts, such as unexpected serialized PHP objects or unusual SQL query patterns.
  6. Harden WordPress installations by restricting file permissions, disabling unnecessary PHP functions, and isolating the web server environment.
  7. Educate site administrators about the risks of using outdated plugins and the importance of timely updates.
  8. Consider implementing Content Security Policy (CSP) and other defense-in-depth measures to limit the impact of potential code execution.
  9. Prepare incident response plans to quickly contain and remediate any detected exploitation.
  10. Engage with cybersecurity vendors or managed security services for advanced threat detection and response capabilities.

Description

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.

References

Community reviews

Loading reviews…