Divi Torque Lite <= 4.2.3 - Cross-Site Request Forgery to Arbitrary Plugin Installation via 'install_plugin' REST Endpoint
Strategic Overview
- Status
- Patched in 4.3.0
- Affected Plugin
- Divi Torque Lite
- Affected Version
<= 4.2.3- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-4275
At a glance
CVE-2026-4275 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Divi Torque Lite WordPress plugin, affecting versions <= 4.2.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.3.0; sites on affected versions should update now. Disclosed July 2026, reported by wesley (wcraft).
Vulnerability Overview
The Divi Torque Lite – Divi Theme, Divi Builder & Extra Theme plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.2.3. This is due to the use of '__return_true' as the permission_callback for the /install_plugin and /activate_plugin REST API endpoints, which bypasses WordPress's built-in REST API nonce verification. Although the endpoint callbacks contain internal current_user_can() checks, the absence of nonce verification means that a forged cross-site request from a logged-in administrator's browser will pass the capability check via the admin's session cookies. This makes it possible for unauthenticated attackers to install arbitrary plugins from WordPress.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Divi Torque Lite <= 4.2.3 carries this weakness at __return_true, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Divi Torque Lite the fix is 4.3.0: builds <= 4.2.3 are affected, anything from 4.3.0 onward is not.
Remediation
Update to version 4.3.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Divi Torque Lite: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Divi Torque Lite 4.3.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Divi Torque Lite
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C