Skip to main content

Themify Builder EUVDEUVD-2026-43139

| CVE-2026-15096 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-07-11 Wordfence GHSA-hr4g-6fjj-w743
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 compromise WordPress contributor account
  2. Delivery
    Access Themify Builder page editor
  3. Exploit
    Inject XSS payload into Map Module b_width_map field
  4. Install
    Save and publish affected page
  5. C2
    Victim user loads injected page
  6. Execute
    Payload executes in victim browser context
  7. Impact
    Exfiltrate session token or execute privileged actions

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 user account with at minimum contributor-level access (PR:L confirmed by CVSS vector). The Themify Builder plugin must be installed and active on the target site. The specific vulnerable component is the Map Module, and the injection point is the b_width_map field within that module. The attacker must have the ability to create or edit pages using the Themify Builder interface - a capability granted to contributors by default in WordPress. What limits exploitation: sites with no contributor-level (or higher) accounts beyond administrators are not practically exploitable; sites with closed user registration and tightly controlled roles face a high barrier; the attack is limited to the Map Module specifically and does not apply to other builder modules. There is no network-level blocking that prevents exploitation since the attack vector is a standard authenticated HTTP POST to the WordPress admin interface.

Impact

The CVSS 3.1 score of 6.4 (Medium) is derived from AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. The PR:L metric correctly reflects the contributor-level authentication barrier, which is the primary limiting factor on real-world risk. On WordPress sites with closed registration or tightly controlled contributor roles, exploitation is difficult. However, many WordPress deployments allow open or semi-open registration, or maintain a large pool of contributors, which lowers the practical barrier significantly. The S:C (Scope Changed) metric captures the cross-context nature of stored XSS - impact falls on the victim's browser, not the server - and UI:N is standard for stored XSS where victim page-load constitutes automatic execution. No EPSS data was provided in the intelligence sources, and the vulnerability is absent from CISA KEV. No POC has been referenced. Taken together, real-world priority is moderate: sites with many contributor accounts or open registration should treat this as urgent; sites with tightly controlled user roles have substantially lower exposure. The authentication requirement is the key differentiator from a critical rating.

Exploit ScenarioDerived

An attacker registers or compromises a contributor-level WordPress account on a site running Themify Builder 7.7.6 or earlier, then uses the builder interface to create or edit a page containing a Map Module, injecting a JavaScript payload such as a cookie-stealing script into the b_width_map field. Once the page is published, every subsequent visitor - including administrators - who loads the page will have the script execute in their browser, potentially exfiltrating their session cookie to an attacker-controlled endpoint and enabling full account takeover of high-privileged users.

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 Cross-Site Scripting in the Themify Builder WordPress plugin (all versions through 7.7.6) enables authenticated attackers holding contributor-level access or higher to persist arbitrary JavaScript via the Map Module's b_width_map field. Because the scope changes (S:C in CVSS), the injected payload executes inside every subsequent visitor's browser context - enabling session hijacking, credential theft, or administrative account takeover against any user who views an affected page. No public exploit code has been identified and this vulnerability is not listed in CISA KEV, but the low exploitation complexity and network-accessible attack surface make it a meaningful risk on sites with open or broad contributor registration.

RemediationAI

The primary remediation is to update the Themify Builder plugin to the version incorporating SVN changeset 3601964 or any later release. Since 7.7.6 is confirmed vulnerable, administrators should update to the next available release and verify against the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/72131ba4-976b-4f89-9a69-2469f22eb5fd) to confirm the patched version - the exact release tag was not independently confirmed in the available data, so consulting the WordPress plugin repository for the current release is required. As a compensating control pending the update, administrators should audit and minimize contributor-level (and above) accounts, restricting access to only trusted users - this eliminates the privilege prerequisite for exploitation. Alternatively, if the Map Module is not actively used on the site, disabling or removing the Themify Builder plugin entirely eliminates the attack surface, though this will break existing pages built with the plugin. There is no known server-side WAF rule that can reliably filter stored XSS input at the WordPress application layer without risk of false positives on legitimate builder content.

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

Themify Builder (CPE: cpe:2.3:a:themifyme:themify_builder:*:*:*:*:*:*:*:*) is a commercial drag-and-drop WordPress page builder plugin. The flaw is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation - Cross-site Scripting). The vulnerability exists across three distinct code paths: template-map.php (line 143, the output/rendering layer), class-themify-builder-active.php (line 559, an intermediate processing class), and class-builder-data-manager.php (line 154, the data persistence layer). This multi-file span indicates the b_width_map parameter reaches persistent storage without sanitization and is subsequently rendered without output escaping, completing a classic stored XSS source-to-sink chain. The Map Module is a visual component that embeds map widgets into builder pages, and the b_width_map field controls map display width - a parameter type developers sometimes overlook for encoding enforcement because it is expected to carry numeric or CSS values.

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

Contributor authentication (PR:L) required; Scope:Changed reflects XSS execution in victim browser; no availability impact; confidentiality and integrity impacts are limited to session-level data and page content.

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:L/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 Map Module 'b_width_map' 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 91% exploitable
Prevalence
Medium
commercial WordPress page builder plugin, moderate market share
Social Media
2
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 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
Medium
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