CVE-2026-11613
Unauthenticated LFI in Divi Ajax Filter allows inclusion and execution of PHP files.
Is CVE-2026-11613 being exploited?
Not confirmed. CVE-2026-11613 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-11613?
CVE-2026-11613 is rated Critical with a CVSS score of 9.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-11613?
Yes. A fix has been recorded for CVE-2026-11613. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11613 affect?
CVE-2026-11613 affects Divi Ajax Filter WordPress plugin <= 5.1.2, WordPress sites with loop_templates set to 'custom-template'. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11613?
Update plugin to fixed version (>5.1.2) or disable plugin; block endpoint with WAF/ACLs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated local file inclusion can include/execute attacker-controlled .php, enabling remote code execution, data theft, and access-control bypass on affected sites.
Immediate action required
- affected<= 5.1.2
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.