CVE-2026-95864 themifyme CVE debrief

Who should care

Defenders responsible for WordPress installations with the Themify Builder plugin should assess exposure and prioritize updates to mitigate this vulnerability. This includes operators managing WordPress environments, platform administrators, vulnerability management teams, and security teams that need to verify and update the plugin to prevent exploitation.

Why it matters

The Themify Builder plugin for WordPress has a Stored Cross-Site Scripting vulnerability, allowing unauthenticated attackers to inject web scripts. Defenders should prioritize verifying and updating the plugin to mitigate this vulnerability.

• Unauthenticated attackers can inject web scripts that execute on page access.
• The vulnerability allows for Stored Cross-Site Scripting attacks.
• Defenders need to verify and update the Themify Builder plugin.
• The nonce is embedded in page markup, weakening access control.

Technical summary

The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'css[fonts]' parameter in all versions up to, and including, 7.8.1. The vulnerability is due to insufficient input sanitization and output escaping. This allows 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. Defenders should prioritize verifying and updating to

Defensive priority

Defenders should prioritize verifying and updating the Themify Builder plugin to mitigate this vulnerability.

Recommended defensive actions

• Verify and update the Themify Builder plugin to the latest version.
• Review and restrict access to the vulnerable endpoint.
• Monitor for suspicious activity and injected scripts.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability is confirmed in versions up to and including 7.8.1 of the Themify Builder plugin. The nonce required to reach the vulnerable endpoint is embedded in plain sight within the front-end page markup.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.