CVE-2026-11613: The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all vulnerability
CVE-2026-11613 affects The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all up to, and including, 5.1.2 via the 'custom_loop_templ The Divi Ajax Filter plugin for WordPress. The published description indicates a remote or...
What happened
CVE-2026-11613 affects The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all up to, and including, 5 1 2 via the 'custom_loop_templ The Divi Ajax Filter plugin for WordPress. A security weakness in The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all is being tracked as CVE-2026-11613. The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 5 1 2 via the 'custom_loop_template' parameter parameter.
The available advisory information identifies up to, and including, 5 1 2 via the 'custom_loop_templ The Divi Ajax Filter plugin for WordPress as affected versions. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all becomes part of the attack condition. The published description indicates a remote or untrusted-network exploitation path.
php files on the server, allowing the execution of any PHP code in those files.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
This makes it possible for unauthenticated attackers to include and execute arbitrary .
php files on the server, allowing the execution of any PHP code in those files.
This can be used to bypass access controls, obtain sensitive data, or achieve
The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 5.1.2 via the 'custom_loop_template' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve
A security weakness in The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all is being tracked as CVE-2026-11613. The available advisory information identifies up to, and including, 5.1.2 via the 'custom_loop_templ The Divi Ajax Filter plugin for WordPress as affected versions. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all becomes part of the attack condition. This makes it possible for unauthenticated attackers to include and execute arbitrary . php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Required condition: an affected The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all up to, and including, 5.1.2 via the 'custom_loop_templ The Divi Ajax Filter plugin for WordPress instance is reachable from a network position available to the attacker.
attacker-controlled network input reaches the vulnerable function on the affected The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all service.
Not publicly disclosed in enough technical detail to describe the mechanism without inference.
Not publicly disclosed in enough detail to state a specific post-exploitation result without inference.
Identify remotely reachable The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all up to, and including, 5.1.2 via the 'custom_loop_templ The Divi Ajax Filter plugin for WordPress; remove unnecessary exposure; apply the vendor fix or mitigation; then review service, network and identity telemetry for exploitation attempts or unexpected follow-on activity.
Why this matters to you
CVE-2026-11613 matters because the practical risk is not the score alone — it is whether The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all up to, and including, 5 exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 9.8. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all up to, and including, 5.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for The Divi Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all up to, and including, 5.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.