dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-4275

HIGH · 8.8 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Divi Torque Lite WordPress plugin uses '__return_true' as the permission_callback for REST API endpoints /install_plugin and /activate_plugin, bypassing WordPress's nonce verification. This enables CSRF attacks where a logged-in administrator's browser can be tricked into installing arbitrary plugins from the WordPress repository via the admin's session cookies.

MitigationUpdate the plugin to version 4.3.0 or later, which replaces the '__return_true' permission_callback with proper nonce verification and capability checks. If patching manually, implement a custom permission_callback that verifies both the nonce and user capabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Divi Torque Lite plugin is installed
    Go to WordPress admin > Plugins and look for 'Divi Torque Lite' in the installed plugins list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and look for 'divi-torque-lite'
    Affected if The plugin appears in the active plugins list
  2. Check the installed plugin version
    In WordPress admin > Plugins > Divi Torque Lite, look at the version number displayed below the plugin name, or query: SELECT option_value FROM wp_options WHERE option_name LIKE '%divi_torque_lite%'
    Affected if The installed version is lower than 4.3.0 (the fixed version)
  3. Inspect the REST API endpoint permission callback
    Examine the plugin files (likely in wp-content/plugins/divi-torque-lite/includes/ or similar) for REST API route registration. Search for 'register_rest_route' calls related to '/install_plugin' or '/activate_plugin' endpoints, then check the 'permission_callback' parameter
    Affected if The permission_callback is set to '__return_true' or any function that unconditionally returns true without nonce verification
  4. Verify nonce verification is missing
    In the identified REST route handler, look for the permission_callback function definition. Confirm it does not call wp_verify_nonce() or check_user_capability() before allowing the install_plugin or activate_plugin actions
    Affected if The permission callback performs no nonce verification and grants access to any authenticated user (even without valid nonce tokens)

A user is affected if Divi Torque Lite is installed with a version lower than 4.3.0 AND the REST API endpoints at /wp-json/divi-torque-lite/install_plugin or /activate_plugin are accessible without nonce verification (permission_callback returns true unconditionally).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 4.3.0 or later, which replaces the '__return_true' permission_callback with proper nonce verification and capability checks. If patching manually, implement a custom permission_callback that verifies both the nonce and user capabilities.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4275 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data