Themify Builder <= 7.7.7 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Stylesheet Write/Delete via tb_generate_on_fly AJAX Action
Strategic Overview
- Status
- Patched in 7.7.8
- Affected Plugin
- Themify Builder
- Affected Version
<= 7.7.7- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-15407
At a glance
CVE-2026-15407 is a medium-severity Missing Authorization vulnerability in the Themify Builder WordPress plugin, affecting versions <= 7.7.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 7.7.8; sites on affected versions should update now. Disclosed July 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.7.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite or delete the generated CSS stylesheet file of arbitrary posts, including private and draft posts owned by other users, and modify plugin-scoped font options. The required CSRF nonce (tf_nonce) is emitted on public front-end builder pages via wp_localize_script, making it trivially obtainable by any authenticated user visiting such a page.
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 interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Themify Builder <= 7.7.7 takes an account at Subscriber level or above. 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.7.8: builds <= 7.7.7 are affected, anything from 7.7.8 onward is not.
Remediation
Update to version 7.7.8, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Themify Builder 7.7.8 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