dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-1454

HIGH · 7.2 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in the Responsive Contact Form Builder plugin for WordPress. The lfb_lead_sanitize() function fails to sanitize certain form field types during input, and the output rendering uses an overly permissive wp_kses() filter that allows dangerous attributes like onclick on anchor tags. This allows unauthenticated attackers to inject malicious JavaScript via form submissions that executes when administrators view lead entries in the dashboard.

MitigationUpdate the plugin to a version beyond 2.0.1 which contains the patched sanitization logic; if immediate update is not possible, consider restricting access to the lead viewing functionality or implementing additional server-side output encoding.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Responsive Contact Form Builder and read the version number displayed. Alternatively, open the main plugin file (e.g., /wp-content/plugins/responsive-contact-form-builder/responsive-contact-form-builder.php) and locate the 'Version:' header in the plugin metadata.
    Affected if The installed version is 2.0.1 or earlier.
  2. Verify the vulnerable sanitization function exists
    Open the plugin file containing lfb_lead_sanitize() function (typically in the main plugin file or includes/leads.php). Search for the function definition and examine whether it properly sanitizes form inputs, particularly checking if it filters dangerous HTML attributes.
    Affected if The lfb_lead_sanitize() function exists and does not sanitize form field inputs or allows dangerous attributes.
  3. Check the output rendering for permissive wp_kses() filter
    Find the code that renders lead entries in the admin dashboard (often in files named lead-view.php, admin-view.php, or similar). Locate where wp_kses() is called and examine the allowed tags and attributes list.
    Affected if The wp_kses() call permits dangerous attributes like onclick, onerror, or allows anchor tags without strict attribute filtering.
  4. Confirm lead viewing functionality is accessible
    Navigate to the WordPress admin dashboard and access the lead viewing section for this plugin (typically under a menu item like 'Contact Form Builder' > 'Leads' or similar). Verify that any logged-in administrator can access submitted form entries.
    Affected if The lead viewing page is accessible and displays submitted form data without additional sanitization beyond the weak wp_kses() filter.
  5. Determine if public form submissions are enabled
    View the published contact form on the frontend of the site (the page where the form is embedded). Attempt to submit a test form entry or check the plugin settings to confirm that form submissions from visitors are accepted.
    Affected if Public form submissions are enabled, as this is the attack vector for injecting malicious scripts.

A user is affected if they have the Responsive Contact Form Builder plugin installed at version 2.0.1 or earlier, the plugin accepts public form submissions, and the lead viewing functionality is accessible to administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 2.0.1 which contains the patched sanitization logic; if immediate update is not possible, consider restricting access to the lead viewing functionality or implementing additional server-side output encoding.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1454 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data