CVE-2026-4275
CSRF in Divi Torque Lite allows attackers to install/activate plugins via an admin session.
Is CVE-2026-4275 being exploited?
Not confirmed. CVE-2026-4275 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-4275?
CVE-2026-4275 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-4275?
Not known from our data. No patch reference has been recorded for CVE-2026-4275, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-4275 affect?
CVE-2026-4275 affects Divi Torque Lite – Divi Theme/Divi Builder & Extra Theme plugin <= 4.2.3, WordPress sites with the affected plugin installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4275?
Remove/disable the plugin and restrict admin access; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Cross-site request forgery lets attackers use a logged-in admin's session to install/activate arbitrary plugins, enabling persistence, remote code execution, or full site compromise.
Immediate action required
- affected<= 4.2.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.