CVE-2026-1454: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in themehunk Lead Form Builder & Contact Form
The Responsive Contact Form Builder & Lead Generation Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.0.1 via form field submissions. This is due to insufficient input sanitization in the lfb_lead_sanitize() function which omits certain field types from its sanitization whitelist, combined with an overly permissive wp_kses() filter at output time that allows onclick attributes on anchor tags. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator views the lead entries in the WordPress dashboard.
AI Analysis
Technical Summary
The Responsive Contact Form Builder & Lead Generation Plugin for WordPress suffers from a stored cross-site scripting vulnerability due to inadequate input sanitization and permissive output filtering. Specifically, the lfb_lead_sanitize() function fails to sanitize certain form field types, and the wp_kses() filter used at output permits onclick attributes on anchor tags. This combination allows unauthenticated attackers to inject arbitrary JavaScript into lead entries, which executes in the context of the WordPress dashboard when viewed by administrators. The vulnerability affects all plugin versions up to and including 2.0.1 and has a CVSS 3.1 base score of 7.2, indicating high severity.
Potential Impact
An attacker can inject persistent malicious scripts into lead form submissions that execute in the administrator's browser when viewing lead entries. This can lead to unauthorized actions such as session hijacking or other client-side attacks impacting confidentiality and integrity. The vulnerability does not affect availability. No known exploits have been reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should exercise caution when viewing lead entries and consider restricting access to the WordPress dashboard. Monitoring for updates from the plugin vendor is recommended to apply any forthcoming patches promptly.
CVE-2026-1454: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in themehunk Lead Form Builder & Contact Form
Description
The Responsive Contact Form Builder & Lead Generation Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.0.1 via form field submissions. This is due to insufficient input sanitization in the lfb_lead_sanitize() function which omits certain field types from its sanitization whitelist, combined with an overly permissive wp_kses() filter at output time that allows onclick attributes on anchor tags. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator views the lead entries in the WordPress dashboard.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Responsive Contact Form Builder & Lead Generation Plugin for WordPress suffers from a stored cross-site scripting vulnerability due to inadequate input sanitization and permissive output filtering. Specifically, the lfb_lead_sanitize() function fails to sanitize certain form field types, and the wp_kses() filter used at output permits onclick attributes on anchor tags. This combination allows unauthenticated attackers to inject arbitrary JavaScript into lead entries, which executes in the context of the WordPress dashboard when viewed by administrators. The vulnerability affects all plugin versions up to and including 2.0.1 and has a CVSS 3.1 base score of 7.2, indicating high severity.
Potential Impact
An attacker can inject persistent malicious scripts into lead form submissions that execute in the administrator's browser when viewing lead entries. This can lead to unauthorized actions such as session hijacking or other client-side attacks impacting confidentiality and integrity. The vulnerability does not affect availability. No known exploits have been reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should exercise caution when viewing lead entries and consider restricting access to the WordPress dashboard. Monitoring for updates from the plugin vendor is recommended to apply any forthcoming patches promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-01-26T19:59:41.414Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69b12b822f860ef94376110d
Added to database: 3/11/2026, 8:44:50 AM
Last enriched: 4/9/2026, 11:19:07 AM
Last updated: 4/25/2026, 3:26:21 PM
Views: 96
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.