Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister subscriber-level account
-
DeliveryVisit public builder page to harvest tf_nonce
-
ExploitCraft authorization-bypass POST request
-
ExecutionOverwrite or delete target post CSS stylesheet
-
ImpactModify plugin font options for site-wide visual impact
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires at minimum a valid subscriber-level authenticated session on the target WordPress site - unauthenticated exploitation is not possible, confirmed by CVSS PR:L. The attacker must also be able to visit at least one public front-end builder page to retrieve the tf_nonce CSRF nonce emitted via wp_localize_script; if all builder pages require higher-privilege authentication, nonce harvesting becomes more constrained. No non-default server configuration is required beyond having the Themify Builder plugin active. Impact is bounded to CSS stylesheet file overwrite/delete and plugin-scoped font option modification - there is no code execution path and no direct data exfiltration. Sites with disabled user registration or no subscriber-level accounts in their user base are not exploitable via this path. |
| Impact | The NVD-assigned CVSS 3.1 score of 4.3 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N accurately reflects the bounded impact: no confidentiality or availability consequence, integrity impact limited to CSS stylesheets and font settings, and a low-privilege authentication requirement that excludes unauthenticated exploitation. Real-world risk is elevated for sites with open user registration, where any registered visitor qualifies as a subscriber and could immediately exploit the flaw. The attack complexity is genuinely low because the required nonce is available on any public builder page - no race condition, no complex precondition. The absence of a KEV listing and the lack of any identified public exploit keep this from being a priority-one response item, but the combination of a large WordPress install base, low exploitation complexity, and the ability to tamper with private/draft post styling (potentially leaking post existence or causing content disruption) warrants prompt patching. EPSS data was not provided in the source intelligence; exploitation probability is therefore inferred rather than quantified. |
| Exploit ScenarioDerived | An attacker registers a free subscriber account on a target WordPress site running Themify Builder 7.7.7 or earlier, then visits any publicly accessible front-end builder page and extracts the tf_nonce value injected by wp_localize_script into the page JavaScript. Using that nonce, the attacker issues crafted HTTP POST requests to the plugin's stylesheet endpoints, deleting or overwriting CSS files for private draft posts authored by other users or altering site-wide font settings, causing visual defacement without triggering any capability check. No public exploit code has been identified at time of analysis, but the attack requires only standard browser developer tools to execute. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 16, 2026
Authorization bypass in the Themify Builder WordPress plugin (all versions through 7.7.7) permits any authenticated subscriber-level user to overwrite or delete CSS stylesheet files for arbitrary posts - including private and draft posts owned by other users - and modify plugin-scoped font options site-wide. The CSRF nonce (tf_nonce) nominally required to gate these actions is broadcast to every authenticated user visiting any public front-end builder page via wp_localize_script, making it trivially collectible and rendering it ineffective as a security control. No active exploitation is confirmed (not in CISA KEV) and no public exploit has been identified at time of analysis.
RemediationAI
An upstream fix has been committed to the Themify Builder plugin repository, as evidenced by the changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3607906%40themify-builder&new=3607906%40themify-builder; however, the specific patched release version number is not independently confirmed from available data - administrators should update to the latest available version from the WordPress plugin repository and verify the installed version exceeds 7.7.7. As a compensating control while awaiting a confirmed patched release, site administrators should disable open user registration if not operationally required, as this eliminates the subscriber-level prerequisite for exploitation; note that this may break workflows relying on self-service registration. Additionally, restricting access to front-end builder pages to authenticated editors or above would prevent the trivial nonce harvesting path, though this trades usability for security. Monitoring for unexpected modifications to CSS stylesheets or font option changes in plugin logs may help detect active exploitation attempts.
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
The vulnerability is rooted in CWE-862 (Missing Authorization) within the Themify Builder WordPress page builder plugin (CPE: cpe:2.3:a:themifyme:themify_builder:*:*:*:*:*:*:*:*). The defective logic resides in class-themify-builder-stylesheet.php, confirmed across at least tags 7.7.5 and 7.7.7 via the plugin's Trac repository at lines 17, 69, 160, and 313. The stylesheet class handles dynamic CSS generation and font option management for builder-created posts. WordPress plugins are expected to call current_user_can() or equivalent capability checks before performing privileged write operations on post-owned resources; this plugin omits those checks. The tf_nonce CSRF token - the sole token protecting these endpoints - is injected into all public front-end builder pages via WordPress's wp_localize_script() function, meaning any authenticated user who loads such a page receives the nonce in the page's HTML, collapsing what should be a multi-layer control into a single, easily bypassed one.
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:U/C:N/I:L/A:N
Subscriber-level authentication required (PR:L); nonce trivially obtained from public pages (AC:L); impact confined to CSS and font integrity with no confidentiality or availability consequence.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
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 Request Forgery exploits the automatic credential inclusion behavior of web browsers.
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More 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 XSS in the Themify Builder WordPress plugin (all versions through 7.7.6) allows contributor-level authenticated u
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 (all versions through 7.7.6) enables authenticated a
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
The Themify Builder plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg
EUVD-2026-44891
GHSA-f4cp-4p46-3f73
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB