Skip to main content

Themify Builder CVE-2026-15097

| EUVDEUVD-2026-43132 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-07-11 Wordfence GHSA-r6f8-v3hv-xx2m
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Recon
    Obtain or register contributor WordPress account
  2. Delivery
    Create or edit page with Themify Builder Slider module
  3. Exploit
    Inject JavaScript into height_slider field
  4. Install
    Payload persists in database
  5. C2
    Victim loads injected page
  6. Execute
    Malicious script executes in victim browser
  7. Impact
    Session tokens or credentials exfiltrated

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
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 an authenticated WordPress session with contributor-level privileges or higher (editor, administrator). The attacker must be able to create or edit pages or posts using the Themify Builder plugin's Slider Module - the height_slider field within that module is the specific injection vector. Sites where contributor registration is open or poorly controlled face the highest risk. Exploitation is bounded by the authentication requirement: unauthenticated visitors and subscriber-level users cannot trigger the stored injection. Payload execution additionally requires a subsequent victim to load the affected page, though this imposes no further constraint on the attacker after initial injection. Non-default configurations that remove contributor create/edit permissions would limit exploitability.

Impact

The CVSS 6.4 score (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects the meaningful but bounded nature of this flaw. Scope:Changed (S:C) elevates the score because injected scripts cross the security boundary into victim browsers, which is the defining characteristic of XSS. However, PR:L constrains real-world risk significantly: an attacker must hold at minimum contributor-level credentials on the target site, ruling out unauthenticated mass exploitation. The attack complexity is genuinely low once access is obtained. No EPSS score was provided in the source data, so exploitation probability cannot be quantified numerically. KEV status is absent, meaning active exploitation is unconfirmed. No standalone public POC is referenced. The practical risk is highest in multi-author WordPress environments with open or weakly controlled contributor registration - single-author or tightly managed sites face substantially reduced exposure. The CVSS UI:N metric is correct from the attacker's perspective (they need no further interaction after injecting the payload), though victim page-visit is required for payload execution.

Exploit ScenarioDerived

An attacker who has registered or compromised a contributor-level WordPress account on a site running Themify Builder ≤7.7.6 creates or edits a page containing a Slider module and injects a JavaScript payload (e.g., a cookie-stealing script) into the height_slider field. The payload is stored in the database and silently executes in the browser of every visitor - including administrators - who subsequently loads that page, allowing the attacker to harvest session tokens without any further interaction.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 11, 2026

Stored XSS in the Themify Builder WordPress plugin (all versions through 7.7.6) allows contributor-level authenticated users to inject persistent JavaScript via the 'height_slider' Slider Module field, which executes in the browser of any visitor who loads an injected page. The scope change (S:C in CVSS) captures the cross-context impact: attacker payload runs in victims' sessions, enabling session hijacking, credential theft, or unauthorized admin actions. No active exploitation is confirmed in CISA KEV, but a patch commit (changeset 3601964) is visible in the WordPress plugin SVN repository, suggesting a fix has been committed beyond version 7.7.6.

RemediationAI

Update the Themify Builder plugin to a version beyond 7.7.6 immediately. A patch commit is confirmed in the WordPress plugin SVN repository at changeset 3601964 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3601964%40themify-builder&new=3601964%40themify-builder); however, the exact released plugin version number containing this fix is not independently confirmed from the available data - verify the current version in the WordPress Plugin Directory before updating. As an interim compensating control, audit and restrict contributor-level role assignments to only fully trusted users, since exploitation requires at minimum contributor access; this reduces the attacker pool but does not eliminate the vulnerability. Site administrators may also temporarily disable the Slider Module within Themify Builder if it is not actively in use, removing the injection surface entirely. Consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/03721b29-7b26-4166-bba1-81614b412a09?source=cve for the latest patch and timeline details.

Affected VersionsENISA

Themify Builder 0 ≤7.7.6

Affected Packages

euvd themify_builder no fix

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 vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS). The affected product is the Themify Builder page-builder plugin for WordPress (CPE: cpe:2.3:a:themifyme:themify_builder:*:*:*:*:*:*:*:*). Source references identify the flaw across multiple plugin files: the height_slider field value is accepted without adequate sanitization in class-builder-data-manager.php (lines 154 and 402) and class-themify-builder-active.php (line 559), then rendered without output escaping in template-slider.php (line 107). The root cause is a failure to apply WordPress sanitization functions (e.g., sanitize_text_field, absint) at input and escaping functions (e.g., esc_attr, esc_html) at output for the slider height parameter, allowing raw script content to persist in the database and execute on page render.

Know when Themify Builder 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 (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.4 MEDIUM

Network-accessible WordPress endpoint, low complexity, contributor auth required (PR:L), scope changes to victim browser; no availability impact from stored XSS.

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

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

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

DescriptionCVE.org

The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'height_slider' Slider Module Field in all versions up to, and including, 7.7.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
High
popular WordPress page builder plugin, broad install base
Social Media
2
Sightings
Data Quality
4 sources
Confidence: Medium

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
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.

Related Vulnerabilities in Themify Builder Stored XSS Vulnerabilities

View all 2

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