CVE-2026-1454
Stored XSS in Responsive Contact Form Builder Plugin Allows Admin Dashboard Script Injection
Publication date: 2026-03-11
Last updated on: 2026-03-11
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Responsive Contact Form Builder & Lead Generation Plugin for WordPress up to version 2.0.1 is vulnerable to Stored Cross-Site Scripting (XSS) via form field submissions.
This vulnerability arises because the input sanitization function lfb_lead_sanitize() does not properly sanitize certain field types, omitting them from its whitelist.
Additionally, the output sanitization uses an overly permissive wp_kses() filter that allows onclick attributes on anchor tags, enabling attackers to inject arbitrary web scripts.
As a result, unauthenticated attackers can inject malicious scripts that execute whenever an administrator views the lead entries in the WordPress dashboard.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to inject and execute arbitrary JavaScript code in the context of the WordPress admin dashboard.
When an administrator views the lead entries, the malicious scripts run, potentially leading to unauthorized actions such as session hijacking, data theft, or further compromise of the WordPress site.
Because the vulnerability affects the admin interface, it can lead to privilege escalation or unauthorized access to sensitive data stored in the lead entries.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability involves Stored Cross-Site Scripting (XSS) via form field submissions in the Responsive Contact Form Builder & Lead Generation Plugin for WordPress (up to version 2.0.1). Detection involves inspecting form submissions and lead entries for injected scripts, especially in the WordPress dashboard where leads are viewed.'}, {'type': 'paragraph', 'content': "Since the vulnerability arises from insufficient input sanitization and overly permissive output filtering, detection can be approached by reviewing the stored lead data for suspicious HTML or JavaScript code, particularly looking for 'onclick' attributes in anchor tags."}, {'type': 'paragraph', 'content': 'There are no explicit commands provided in the resources for automated detection on the network or system. However, administrators can manually check the database table storing lead data (likely `LFB_FORM_DATA_TBL`) for entries containing suspicious script tags or event handlers.'}, {'type': 'paragraph', 'content': 'Additionally, monitoring HTTP requests to the form submission endpoints for unusual payloads containing script tags or JavaScript event handlers could help detect exploitation attempts.'}] [1, 2, 4]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'The primary mitigation step is to update the Responsive Contact Form Builder & Lead Generation Plugin to version 2.0.3 or later, where the vulnerability has been fixed by applying proper input sanitization, output escaping, and access control checks.'}, {'type': 'list_item', 'content': "Ensure that only authorized users with the 'manage_options' capability can view lead entries, preventing unauthorized access."}, {'type': 'list_item', 'content': 'Apply proper escaping functions such as esc_html() and esc_attr() on all dynamic output related to lead data to prevent script injection.'}, {'type': 'list_item', 'content': 'Sanitize all user inputs on form submission, including file uploads and multi-value fields, using WordPress sanitization functions.'}, {'type': 'list_item', 'content': 'If immediate update is not possible, consider disabling the plugin or restricting access to the lead viewing pages to trusted administrators only.'}, {'type': 'paragraph', 'content': 'Also, review and remove any suspicious lead entries that may contain malicious scripts to prevent execution when viewed.'}] [4]