CVE-2024-7780: Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (WordPress plugin) · SQL Injection
Affects Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| bitpressadmin Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-7780, organizations should first check for and apply any official patches or updates from the plugin vendor once available. In the absence of patches, administrators should consider temporarily disabling or removing the affected plugin to eliminate the attack vector. Restrict administrative access strictly by enforcing strong authentication methods such as multi-factor authentication (MFA) and regularly auditing admin accounts for suspicious activity. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'id' parameter in the plugin's requests. Review and harden database user permissions to limit the impact of potential SQL injection, ensuring the WordPress database user has only necessary privileges. Additionally, monitor logs for unusual SQL query patterns or access attempts to the plugin's endpoints. Consider isolating the WordPress environment and backing up data regularly to enable rapid recovery if compromise occurs. Finally, educate site administrators on the risks of privilege escalation and the importance of plugin security hygiene.
Description
The Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder plugin for WordPress is vulnerable to generic SQL Injection via the id parameter in versions 2.0 to 2.13.9 due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
References
- wordfence.com/threat-intel/vulnerabilities/id/73b6b22a-4699-4307-8a03-148dd9e95d36?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/bit-form/tags/2.13.6/includes/Admin/AdminAjax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bit-form/tags/2.13.6/includes/Admin/Form/AdminFormHandler.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bit-form/tags/2.13.6/includes/Core/Messages/EmailTemplateHandler.php (opens in a new tab)