CVE-2026-4275: CWE-352 Cross-Site Request Forgery (CSRF) in badhonrocks Divi Torque Lite – Divi Modules for the Divi Builder & Theme
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.
AI Analysis
Technical Summary
The Divi Torque Lite WordPress plugin versions up to 4.2.3 are vulnerable to CSRF due to the use of '__return_true' as the permission_callback for critical REST API endpoints related to plugin installation and activation. This bypasses the standard WordPress REST API nonce verification mechanism. Although internal capability checks (current_user_can()) exist, the absence of nonce verification allows an attacker to leverage a logged-in administrator's session cookies to perform unauthorized actions. This vulnerability enables remote attackers to install arbitrary plugins via forged requests without authentication.
Potential Impact
Successful exploitation allows an attacker to install arbitrary plugins on the affected WordPress site by exploiting the administrator's authenticated session. This can lead to full site compromise, including code execution, data theft, or site defacement. The vulnerability affects confidentiality, integrity, and availability of the site.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
CVE-2026-4275: CWE-352 Cross-Site Request Forgery (CSRF) in badhonrocks Divi Torque Lite – Divi Modules for the Divi Builder & Theme
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.
CVSS v3.1
Score 8.8high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Divi Torque Lite WordPress plugin versions up to 4.2.3 are vulnerable to CSRF due to the use of '__return_true' as the permission_callback for critical REST API endpoints related to plugin installation and activation. This bypasses the standard WordPress REST API nonce verification mechanism. Although internal capability checks (current_user_can()) exist, the absence of nonce verification allows an attacker to leverage a logged-in administrator's session cookies to perform unauthorized actions. This vulnerability enables remote attackers to install arbitrary plugins via forged requests without authentication.
Potential Impact
Successful exploitation allows an attacker to install arbitrary plugins on the affected WordPress site by exploiting the administrator's authenticated session. This can lead to full site compromise, including code execution, data theft, or site defacement. The vulnerability affects confidentiality, integrity, and availability of the site.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-16T15:20:23.202Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4f797f68715ace432894e2
Added to database: 07/09/2026, 10:35:43 UTC
Last enriched: 07/09/2026, 10:47:42 UTC
Last updated: 08/23/2026, 10:52:09 UTC
Views: 85
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.