Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain or compromise WordPress contributor account
-
DeliveryAccess Themify Builder page editor
-
ExploitInject XSS payload into Map Module b_width_map field
-
InstallSave and publish affected page
-
C2Victim user loads injected page
-
ExecutePayload executes in victim browser context
-
ImpactExfiltrate 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 |
| 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 |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
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.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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 2More in Themify Builder
View allAuthenticated Contributor-level users can exploit a PHP Object Injection vulnerability in Themify Builder versions up to
Stored cross-site scripting in the Themify Builder plugin for WordPress, affecting all versions up to and including 7.8.
Reflected cross-site scripting in the Themify Builder WordPress plugin (versions up to and including 7.7.4) lets remote
Stored cross-site scripting in the Themify Builder plugin for WordPress (all versions through 7.8.2) allows an authentic
Stored cross-site scripting in the Themify Builder WordPress plugin affects all versions up to and including 7.8.4: auth
Unauthenticated styling data manipulation in the Themify Builder WordPress plugin (all versions through 7.8.0) allows an
Authorization bypass in the Themify Builder WordPress plugin (all versions through 7.7.7) permits any authenticated subs
The Themify Builder plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg
EUVD-2026-43139
GHSA-hr4g-6fjj-w743
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB