Thrive Visual Editor <= 10.9.3.1 - Unauthenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 10.9.3.2
- Affected Plugin
- Thrive Visual Editor
- Affected Version
<= 10.9.3.1- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-66694
At a glance
CVE-2026-66694 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Thrive Visual Editor WordPress plugin, affecting versions <= 10.9.3.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.9.3.2; sites on affected versions should update now. Disclosed August 2026, reported by dutafi.
Vulnerability Overview
The Thrive Visual Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 10.9.3.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.
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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Thrive Visual Editor <= 10.9.3.1 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Thrive Visual Editor the fix is 10.9.3.2: builds <= 10.9.3.1 are affected, anything from 10.9.3.2 onward is not.
Remediation
Update to version 10.9.3.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Thrive Visual Editor 10.9.3.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Thrive Visual Editor
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C