CVE-2026-129096 in Themify Builder Plugin
Summary
by MITRE • 11/21/2026
The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 7.8.5 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The Themify Builder plugin for WordPress represents a significant attack surface within the widely used content management system ecosystem due to its extensive functionality in designing website layouts. The identified vulnerability stems from insufficient input sanitization and output escaping mechanisms embedded within the plugin's core architecture, specifically affecting the data parameter across all versions up through 7.8.5. This technical flaw allows for Stored Cross-Site Scripting, a severe class of injection attacks where malicious scripts are permanently stored on the target server rather than being executed immediately via a crafted link. The root cause lies in the failure to properly validate and encode user-supplied data before it is processed by the application logic and subsequently rendered back to users without adequate sanitization checks.
From an operational perspective, this vulnerability enables authenticated attackers with contributor-level access or higher privileges to inject arbitrary web scripts into pages managed by the Themify Builder. Unlike reflected XSS attacks that require social engineering to trick a user into clicking a malicious link, stored vulnerabilities persist on the server side. Consequently, every time any user accesses a page containing the injected script, the malicious code executes within their browser context under the trust relationship established with the WordPress site. This persistence transforms the vulnerability from an isolated incident into a continuous threat vector that can compromise numerous users over an extended period without further interaction from the attacker.
The impact of this exploitation is multifaceted and potentially devastating for both end-users and website administrators. Attackers can leverage the executed scripts to perform session hijacking by stealing authentication cookies, thereby gaining unauthorized access to user accounts with elevated privileges. Furthermore, the malicious code can be used to deface web pages, redirect users to phishing sites designed to harvest credentials or distribute malware, or manipulate page content to deceive visitors into performing unintended actions such as transferring funds or downloading infected files. The ability to execute scripts in the context of the victim's browser also allows attackers to bypass same-origin policy restrictions, potentially accessing sensitive data stored locally by other applications running on the user's device if additional vulnerabilities are present.
This vulnerability aligns with CWE-79, which classifies Improper Neutralization of Input During Web Page Generation as a critical weakness in web application security. The specific attack vector corresponds to MITRE ATT&CK technique T1059, specifically sub-technique 007 for Command and Scripting Interpretation via JavaScript within the browser environment. It also relates to T1189 Drive-by Compromise if the script facilitates further malware delivery, and T1204 User Execution if it tricks users into initiating malicious actions. The lack of proper output escaping violates fundamental security principles regarding data integrity and trust boundaries in web applications.
Mitigation strategies must prioritize immediate remediation through software updates alongside robust defensive coding practices. Administrators should upgrade the Themify Builder plugin to version 7.8.6 or later, where these input validation and output encoding flaws have been addressed by the developers. In environments where upgrading is not immediately feasible, implementing a Web Application Firewall can provide an additional layer of defense by filtering out malicious payloads targeting the vulnerable data parameter before they reach the application logic. Furthermore, enforcing strict Content Security Policy headers can help mitigate the impact of any successful exploitation by restricting the sources from which scripts are allowed to execute. Regular security audits and code reviews focusing on input sanitization and output escaping mechanisms are essential for preventing similar vulnerabilities in future development cycles.