Skip to main content

Themify Builder CVE-2026-95864

| EUVDEUVD-2026-86580 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-09-25 Wordfence GHSA-h25g-w4w9-f766
7.2
CVSS 3.1 · Vendor: Wordfence
Share

Severity by source

Vendor (Wordfence) PRIMARY
7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI
7.2 HIGH

Nonce is publicly exposed in markup so PR:N; stored XSS crosses into the visitor's browser (S:C) with partial confidentiality/integrity impact and no availability effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

2
Analysis Generated
Sep 25, 2026 - 08:19 vuln.today
CVE Published
Sep 25, 2026 - 07:40 cve.org
HIGH 7.2

DescriptionCVE.org

The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'css[fonts]' Parameter in all versions up to, and including, 7.8.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The nonce required to reach the vulnerable endpoint is embedded in plain sight within the front-end page markup for all visitors, reducing the access control to a CSRF token rather than an authentication barrier and making the endpoint fully exploitable by unauthenticated attackers.

AnalysisAI

Stored cross-site scripting in the Themify Builder plugin for WordPress, affecting all versions up to and including 7.8.1, allows unauthenticated attackers to inject arbitrary JavaScript through the css[fonts] parameter; the payload is persisted in site styling and executes in the browser of any visitor who later views the affected page. The assessed CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, score 7.2) confirms this is a network-reachable, unauthenticated attack requiring no victim interaction to plant the payload, with scope change because the injected content escapes the plugin's own security boundary into site pages. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

No credit card · 7-day full trial

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitable against default configurations of any site running Themify Builder <=7.8.1 where the vulnerable styling endpoint is reachable and the front-end pages expose the nonce in markup (the described default behavior). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment This is a genuine but moderate-severity issue rather than an emergency. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation An upstream fix for this issue exists in the plugin's Trac repository as changeset 3710320 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3710320%40themify-builder&new=3710320%40themify-builder), so the primary action is to update Themify Builder to the first release containing that changeset; the exact patched version number is not independently confirmed in the provided data, so verify the installed version against the changelog and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/fc021ee6-694a-426b-b399-8dd015fd99d2?source=cve before assuming remediation. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within the first 24 hours, inventory every WordPress instance running Themify Builder at or below version 7.8.1 and deactivate the plugin on any site that does not absolutely require it, or, where it is business-critical, place the affected sites behind a WAF rule that blocks or sanitizes requests carrying the css[fonts] parameter; simultaneously run an immediate content scan of stored styling and theme/page post metadata for injected script tags or obfuscated JavaScript, back up current databases for forensic comparison, and notify the web operations and communications owners that the plugin is unpatched. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-95864 vulnerability details – vuln.today

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