Themify Builder <= 7.8.0 - Missing Authorization to Unauthenticated Arbitrary Builder Data Modification via 'tb_update_old_data' AJAX Action
Strategic Overview
- Status
- Patched in 7.8.1
- Affected Plugin
- Themify Builder
- Affected Version
<= 7.8.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-75027
At a glance
CVE-2026-75027 is a medium-severity Missing Authorization vulnerability in the Themify Builder WordPress plugin, affecting versions <= 7.8.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.8.1; sites on affected versions should update now. Disclosed August 2026, reported by Wordfence PRISM.
Vulnerability Overview
The Themify Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.8.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to modify the stored Themify Builder styling data (padding and margin properties) of arbitrary posts, including private and draft posts, by supplying an attacker-controlled post ID and JSON styling payload. The nonce required by the handler is automatically emitted to all frontend pages rendered by the builder via wp_localize_script, meaning any unauthenticated visitor can trivially retrieve a valid nonce from page source and satisfy the only access control in place.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Themify Builder <= 7.8.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Themify Builder the fix is 7.8.1: builds <= 7.8.0 are affected, anything from 7.8.1 onward is not.
Remediation
Update to version 7.8.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Themify Builder 7.8.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Themify Builder
- 8.8CVE-2024-56216: Themify Builder <= 7.6.3 Local File Inclusion
CVE-2024-56216 - 7.2CVE-2026-57369: Themify Builder <= 7.7.4 Stored Cross-Site Scripting
CVE-2026-57369 - 6.4CVE-2026-15096: Themify Builder <= 7.7.6 Stored Cross-Site Scripting
CVE-2026-15096 - 6.4CVE-2026-15097: Themify Builder <= 7.7.6 Stored Cross-Site Scripting
CVE-2026-15097 - 6.4CVE-2025-9353: Themify Builder <= 7.6.9 Stored Cross-Site Scripting
CVE-2025-9353 - 6.4CVE-2024-52423: Themify Builder <= 7.6.5 Stored Cross-Site Scripting
CVE-2024-52423 - 6.1CVE-2024-13319: Themify Builder <= 7.6.5 Reflected XSS
CVE-2024-13319 - 6.1CVE-2024-9385: Themify Builder <= 7.6.2 Reflected Cross-Site Scripting
CVE-2024-9385
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C