Skip to main content

Free Theme Builder for Elementor CVE-2026-11767

| EUVDEUVD-2026-46159 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-07-21 WPScan GHSA-9g9m-xxjx-jx22
8.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Locate plugin contact form on target site
  2. Delivery
    Submit form field with stored XSS payload
  3. Exploit
    Payload persisted unsanitized in database
  4. Execution
    Admin opens submissions in wp-admin
  5. Persist
    Script executes in admin session
  6. Impact
    Hijack session or forge admin actions

Vulnerability Assessment

Weakness
CWE
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the target WordPress site to run Free Theme Builder for Elementor before 1.6.7 with a public-facing contact form provided by the plugin; the attacker submits a crafted value into a contact form field, no authentication needed (PR:N). The decisive LIMITING factor is user interaction (UI:R): the payload only fires when a logged-in administrator opens the form-submissions view in the admin dashboard - it does not self-trigger. There are no privilege or configuration prerequisites for injection, but exploitation is bounded by the presence of an active plugin-provided form and an admin who reviews submissions.

Impact

Signals conflict, so prioritize with care. The NVD CVSS of 8.8 with C:H/I:H/A:H overstates the direct impact of a stored XSS: for a script executing in an admin's browser, confidentiality/integrity impact is realistically partial (session/action abuse) rather than total system compromise, and availability impact is doubtful - the vector's H/H/H ratings look inflated for this bug class. Countervailing signals point to lower urgency: EPSS is only 0.17% (7th percentile), SSVC exploitation status is 'none' and automatable is 'no', meaning no observed automated exploitation. The mitigating factor is real: exploitation requires an administrator to view the malicious submission (UI:R). Conversely, SSVC technical impact is rated 'total' and public POC code exists, so a successful hit against an active admin could be serious. Net: a genuine, patchable issue worth remediating in normal cycles, but not an emergency - this is a high-CVSS/low-real-world-probability case, not a KEV-grade threat.

Exploit ScenarioDerived

An anonymous attacker submits the site's public contact form with a field value containing a JavaScript payload (e.g., an event-handler-laden HTML string) instead of normal text. The plugin stores the value verbatim; when an administrator later opens the form submissions in wp-admin, the script executes in their authenticated session, allowing the attacker to steal cookies, forge admin requests (create users, install plugins), or pivot to full site takeover. Publicly available POC code from WPScan demonstrates the injection; the network attack vector and low complexity make the injection trivial, with the only gate being that an admin must view the submission.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 22, 2026

Stored cross-site scripting in the Free Theme Builder for Elementor WordPress plugin before 1.6.7 lets unauthenticated attackers inject malicious script through contact form field values, which are stored unsanitized and later rendered in the admin dashboard's form-submissions view. The payload executes in the browser of any logged-in administrator who reviews submissions, enabling session hijacking or actions in the admin's context. Publicly available exploit code exists (WPScan), but there is no evidence of active exploitation and EPSS probability is low (0.17%).

RemediationAI

Upgrade the Free Theme Builder for Elementor plugin to version 1.6.7 or later - Vendor-released patch: 1.6.7 resolves the stored XSS. If immediate patching is not possible, apply specific compensating controls: temporarily deactivate the plugin's contact form functionality or the plugin itself (side effect: front-end forms and theme-building features stop working); restrict access to the wp-admin form-submissions page so only trusted administrators view it, and avoid opening unreviewed submissions until patched; and deploy a WAF rule to strip or encode script/HTML in form field submissions (side effect: may reject legitimate input containing angle brackets). A Content-Security-Policy that disallows inline script in wp-admin further reduces payload execution but can break other admin plugins. Reference the WPScan advisory (https://wpscan.com/vulnerability/e06a6497-e44f-43b9-b6ba-407aea171387/) and NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-11767) for details.

Affected VersionsENISA

Free Theme Builder for Elementor 0 <1.6.7

Affected Packages

euvd free_theme_builder_for_elementor fix: 1.6.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin that adds theme-building and contact-form capabilities to the Elementor page builder ecosystem. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation): submitted contact-form field values are persisted to the database and echoed back into the wp-admin submissions listing without output encoding or input sanitization. Because the sink is the authenticated admin dashboard while the source is an anonymous front-end form, this is a classic stored/persistent XSS where a low-privileged (unauthenticated) actor plants a payload that later fires in a high-privileged context. CPE cpe:2.3:a:unknown:free_theme_builder_for_elementor:*:*:*:*:*:*:*:* identifies the affected package; note the NVD description text calls it 'Free Builder for Elementor' while the CPE, tags, and EUVD consistently name it 'Free Theme Builder for Elementor'.

Know when Free Theme Builder For Elementor gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 6.1 MEDIUM

Unauthenticated injection over the network (PR:N/AV:N/AC:L) but requires an admin to view submissions (UI:R); script crosses into the admin security context (S:C) with partial confidentiality/integrity impact typical of XSS and no availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Patch available
Jul 21, 2026 - 08:02 EUVD
CVE Published
Jul 21, 2026 - 06:00 cve.org
HIGH 8.8
CVE Published
Jul 21, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Free Builder for Elementor WordPress plugin before 1.6.7 does not sanitise submitted contact form field values before storing them and outputting them in the admin dashboard, allowing unauthenticated attackers to perform Stored Cross-Site Scripting attacks that execute when a logged-in administrator views the form submissions.

Executive ViewAI

Why It Matters

Free Theme Builder for Elementor WordPress plugin versions before 1.6.7 contains a stored XSS vulnerability allowing attackers to compromise administrator accounts through contact form submissions. Publicly available exploit code exists, though no active exploitation is currently documented. This poses significant risk to WordPress sites using the plugin, with potential for account takeover and unauthorized administrative actions.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
niche WordPress/Elementor add-on plugin, moderate but not universal install base
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy