Contact Form & Lead Form Elementor Builder <= 1.6.3 - Unauthenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.6.4
- Affected Plugin
- Lead Form Builder & Contact Form
- Affected Version
<= 1.6.3- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24967
At a glance
CVE-2021-24967 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Lead Form Builder & Contact Form WordPress plugin, affecting versions <= 1.6.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.6.4; sites on affected versions should update now. Disclosed November 2021, reported by Krzysztof Zając.
Vulnerability Overview
The Contact Form & Lead Form Elementor Builder WordPress plugin before 1.6.4 does not sanitise and escape some lead values, which could allow unauthenticated users to perform Cross-Site Scripting attacks against logged in admin viewing the inserted Leads
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, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Lead Form Builder & Contact Form <= 1.6.3 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Lead Form Builder & Contact Form the fix is 1.6.4: builds <= 1.6.3 are affected, anything from 1.6.4 onward is not.
Remediation
Update to version 1.6.4, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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.6.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 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 - 6.6CVE-2024-3637: Responsive Contact Form Builder & Lead… Stored XSS
CVE-2024-3637 - 4.4CVE-2024-10475: Responsive Contact Form Builder & Lead… Stored XSS
CVE-2024-10475
Other vulnerabilities in Lead Form Builder & Contact Form
- 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-2022-23179: Responsive Contact Form Builder & Lead… Stored XSS
CVE-2022-23179 - 4.3CVE-2025-68046: Contact Form & Lead Form… Information Exposure
CVE-2025-68046 - 4.3CVE-2024-1416: Responsive Contact Form… Missing Authorization
CVE-2024-1416 - 4.3CVE-2024-1415: Responsive Contact Form Builder & Lead Generation CSRF
CVE-2024-1415
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C