CVE-2026-4275

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-09. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 9, 2026

References (8)

Vendor Advisories for CVE-2026-4275(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-01 14:44 UTCEG score recompute
  2. 2026-08-01 14:44 UTCGHSA enrichment
  3. 2026-08-01 04:16 UTCEPSS rescore
  4. 2026-08-01 01:45 UTCGHSA enrichment
  5. 2026-07-31 12:11 UTCGHSA enrichment
  6. 2026-07-30 23:13 UTCEG score recompute
  7. 2026-07-30 23:13 UTCGHSA enrichment
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 10:14 UTCEG score recompute
  10. 2026-07-30 10:14 UTCGHSA enrichment
  11. 2026-07-30 01:30 UTCEPSS rescore
  12. 2026-07-29 21:15 UTCGHSA enrichment
  13. 2026-07-29 06:43 UTCGHSA enrichment
  14. 2026-07-28 17:45 UTCEG score recompute
  15. 2026-07-28 17:45 UTCGHSA enrichment
  16. 2026-07-28 15:37 UTCEPSS rescore
  17. 2026-07-28 04:44 UTCGHSA enrichment
  18. 2026-07-27 15:36 UTCEG score recompute
  19. 2026-07-27 15:36 UTCGHSA enrichment
  20. 2026-07-27 01:21 UTCEG score recompute
  21. 2026-07-27 01:20 UTCGHSA enrichment
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 12:21 UTCEG score recompute
  24. 2026-07-26 12:21 UTCGHSA enrichment
  25. 2026-07-25 14:18 UTCEPSS rescore
Show 35 more
  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:11 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-17 00:28 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 11:29 UTCGHSA enrichment
  14. 2026-07-15 22:31 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 09:32 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-14 20:28 UTCGHSA enrichment
  21. 2026-07-14 07:30 UTCGHSA enrichment
  22. 2026-07-13 22:30 UTCEPSS rescore
  23. 2026-07-13 18:30 UTCGHSA enrichment
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-13 05:31 UTCGHSA enrichment
  26. 2026-07-12 16:33 UTCGHSA enrichment
  27. 2026-07-12 05:46 UTCEPSS rescore
  28. 2026-07-12 03:34 UTCGHSA enrichment
  29. 2026-07-11 14:34 UTCGHSA enrichment
  30. 2026-07-11 08:27 UTCEPSS rescore
  31. 2026-07-11 01:36 UTCGHSA enrichment
  32. 2026-07-10 12:35 UTCGHSA enrichment
  33. 2026-07-09 23:36 UTCGHSA enrichment
  34. 2026-07-09 10:38 UTCEG score recompute
  35. 2026-07-09 10:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-4275?
CVE-2026-4275 is a high vulnerability published on July 9, 2026. 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 'returntrue' as the permissioncallback for the /installplugin and /activateplugin REST API endpoints,…
When was CVE-2026-4275 disclosed?
CVE-2026-4275 was first published in the National Vulnerability Database on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4275 actively exploited?
CVE-2026-4275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.4% of all scored CVEs.
What is the CVSS score of CVE-2026-4275?
CVE-2026-4275 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-4275?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4275, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-4275

Explore →

Is Your Infrastructure Affected by CVE-2026-4275?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs