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
Share

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

Lifecycle Timeline

2
Analysis Generated
Jul 11, 2026 - 05:15 vuln.today
CVE Published
Jul 11, 2026 - 03:44 cve.org
MEDIUM 6.4

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.

AnalysisAI

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.

Technical ContextAI

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.

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.

Share

EUVD-2026-43139 vulnerability details – vuln.today

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