Security readout for executives and security teams
Plain-English summary
A WordPress contact form plugin can store malicious script submitted through public forms. When an administrator views lead entries in the dashboard, that script can run in the admin’s browser. This creates risk to site administration and data handled in WordPress, especially on public-facing sites using affected plugin versions.
Executive priority
Treat as high priority for public WordPress sites using this plugin. The issue can turn ordinary form submissions into code execution in an administrator’s browser, potentially affecting site integrity and administrative trust. Prioritize inventory, update or disablement, and review of stored leads.
Technical view
CVE-2026-1454 is stored XSS in ThemeHunk Lead Form Builder & Contact Form, reported for versions up to and including 2.0.1. The issue involves incomplete sanitization in lfb_lead_sanitize() and permissive output filtering allowing onclick attributes on anchor tags. The CVSS 3.1 score is 7.2, high.
Likely exposure
Public WordPress sites using Responsive Contact Form Builder / Lead Form Builder & Contact Form up to 2.0.1 are exposed, especially where unauthenticated visitors can submit forms and administrators review leads in WordPress.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not marked KEV. Exploitation requires malicious content to be stored through a form submission and later rendered in an administrator-facing lead view.
Researcher notes
The evidence points to sanitization gaps in form submission handling and unsafe rendering in the lead display path. The provided references include the vulnerable code locations and a WordPress plugin repository changeset. The bundle does not provide a named fixed version or proof of exploitation in the wild.
Mitigation direction
- Inventory WordPress sites for the affected plugin and version.
- Upgrade beyond version 2.0.1 if a vendor-approved fixed release is available.
- If no safe update is available, disable the plugin until vendor guidance is confirmed.
- Restrict administrator access and review of leads to trusted networks where feasible.
- Monitor vendor, WordPress plugin repository, and Wordfence guidance for remediation details.
Validation and detection
- Confirm whether the plugin is installed and active on each WordPress site.
- Record the installed plugin version and compare it to 2.0.1.
- Review stored lead entries for unexpected links, event attributes, or script-like content.
- Check WordPress admin activity logs for unusual actions after lead review.
- Verify the deployed plugin includes the referenced changeset or later vendor fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1454 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f5863132-90a7-414f-abcb-e8b6a9d229c5?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/lead-form-builder/tags/2.0.1/inc/ajax-functions.php#L587CVE reference
- https://plugins.trac.wordpress.org/browser/lead-form-builder/tags/2.0.1/inc/show-lead.php#L13CVE reference
- https://plugins.trac.wordpress.org/changeset/3462549/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
