Responsive Contact Form Builder & Lead Generation Plugin <= 1.8.9 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.9.0
- Affected Plugin
- Lead Form Builder & Contact Form
- Affected Version
<= 1.8.9- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-1415
At a glance
CVE-2024-1415 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Lead Form Builder & Contact Form WordPress plugin, affecting versions <= 1.8.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.9.0; sites on affected versions should update now. Disclosed April 2024, reported by Duc Manh.
Vulnerability Overview
The Responsive Contact Form Builder & Lead Generation Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.8.9. This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated attackers to invoke those functions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. These actions may result in form deletion, and lead signup as well as file upload.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Lead Form Builder & Contact Form <= 1.8.9 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Lead Form Builder & Contact Form the fix is 1.9.0: builds <= 1.8.9 are affected, anything from 1.9.0 onward is not.
Remediation
Update to version 1.9.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Lead Form Builder & Contact Form: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Lead Form Builder & Contact Form 1.9.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Lead Form Builder & Contact Form
- 7.2CVE-2026-32532: Lead Form Builder & Contact Form <= 2.0.1 Stored XSS
CVE-2026-32532 - 7.2CVE-2026-1454: Responsive Contact Form Builder & Lead… Stored XSS
CVE-2026-1454 - 7.2CVE-2021-24967: Contact Form & Lead Form Elementor Builder Stored XSS
CVE-2021-24967 - 6.6CVE-2024-3637: Responsive Contact Form Builder & Lead… Stored XSS
CVE-2024-3637 - 6.5CVE-2023-25969: Multiple Plugins By ThemeHunk Missing Authorization
CVE-2023-25969 - 6.3CVE-2022-23180: Contact Form & Lead Form… Arbitrary Settings Change
CVE-2022-23180 - 5.4CVE-2024-4261: Responsive Contact Form… Arbitrary Shortcode Execution
CVE-2024-4261 - 4.4CVE-2024-10475: Responsive Contact Form Builder & Lead… Stored XSS
CVE-2024-10475
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C