Skip to main content
VulnerabilityPublished Updated

CVE-2023-2655: Contact Form by WD (WordPress plugin) · SQL Injection

Affects Contact Form by WD (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jan 2024

  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
Unknown Contact Form by WDAffected
  • =0
Fixed in–

AI-suggested

  1. Immediate patching: Organizations should update the Contact Form by WD plugin to the latest version once a patch is released. In the absence of an official patch, consider temporarily disabling the plugin or replacing it with an alternative contact form solution.
  2. Privilege management: Restrict administrative privileges strictly to trusted users and implement multi-factor authentication (MFA) to reduce the risk of credential compromise.
  3. Input validation: Implement additional web application firewall (WAF) rules to detect and block suspicious SQL injection attempts targeting the plugin’s endpoints.
  4. Database permissions: Limit database user permissions associated with the WordPress application to the minimum necessary to reduce the impact of SQL injection.
  5. Monitoring and logging: Enable detailed logging of database queries and WordPress admin activities to detect anomalous behavior indicative of exploitation attempts.
  6. Security audits: Conduct regular vulnerability scans and penetration tests focusing on WordPress plugins and custom code to identify similar injection flaws.

Description

The Contact Form by WD WordPress plugin through 1.13.23 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin

References

Community reviews

Loading reviews…