Radar sectionsDatabase
Check my site
WordPress plugin

Divi Torque Lite <= 4.2.3 — Cross-Site Request Forgery to Arbitrary Plugin Installation via 'install_plugin' REST Endpoint

CVE-2026-4275Published · Updated

Action summary

Affected: ≤4.2.3Update to 4.3.0 or newer

All remediation steps
Severity
High8.8
CVSS
8.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-352 CSRF
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Divi Torque Lite addons-for-divi

  1. Affected≤ 4.2.3
  2. Patched in4.3.0

Update to 4.3.0 or newer.

You are affected if you run ≤ 4.2.3. Version 4.3.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Divi Torque Lite.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 4.3.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Divi Torque Lite to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to wesley (wcraft).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Divi Torque Lite

All 5
More vulnerabilities in Divi Torque Lite
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via Magnific Popups JavaScript Library
≤6.0.4Update to 6.0.5
CVE-2024-5647
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via Multiple Widgets
≤4.1.0Update to 4.1.1
CVE-2025-0353
Medium6.4Authenticated (Author+) Stored Cross-Site Scripting via SVG Upload
≤3.6.6Update to 4.0.0
CVE-2024-5892
Medium6.3Missing Authorization Checks
all versionsNo patch available
CVE-2022-4974

Same weakness (CSRF)

All CSRF
Other CSRF vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 8.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?