CVE-2026-4275: Divi Torque Lite (WordPress plugin) · Cross-Site Request Forgery (CSRF)
Affects Divi Torque Lite (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| badhonrocksDivi Torque Lite – Divi Modules for the Divi Builder & Theme | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, administrators should restrict access to the REST API endpoints or disable the vulnerable plugin. Additionally, monitoring for suspicious plugin installations and limiting administrator sessions can reduce risk.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/8be98cba-b891-42cf-8a6c-8fe05f27c9c3?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/addons-for-divi/tags/4.2.2/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/addons-for-divi/trunk/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/addons-for-divi/trunk/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/addons-for-divi/tags/4.2.2/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/addons-for-divi/trunk/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/addons-for-divi/tags/4.2.2/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3559041%40addons-for-divi&new=3559041%40addons-for-divi (opens in a new tab)