Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-11613 – Unauthenticated Local File Inclusion / RCE – Divi Ajax Filter WordPress Plugin ≤ 5.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-11613 is a critical Local File Inclusion (LFI) vulnerability in the Divi Ajax Filter WordPress plugin, developed by Divi Engine, affecting all versions up to and including 5.1.2. The flaw allows unauthenticated attackers to remotely include and execute arbitrary PHP files on the server via a crafted request, which can lead to full remote code execution. The issue carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin fails to properly validate/sanitize the custom_loop_template parameter before using it in a PHP file-include operation, classified as CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program).
  • Trigger condition: The vulnerable code path is reached when the loop_templates parameter is set to custom-template, at which point the custom_loop_template value is used to determine the file to include.
  • Attack vector: Network-based, requires no authentication and no user interaction — an attacker can send a specially crafted AJAX request directly to a vulnerable WordPress site running the plugin.
  • Impact: Successful exploitation allows an attacker to include and execute arbitrary .php files present on the server (local file inclusion), enabling execution of any PHP code contained in those files. Depending on what files exist on the target server, this can escalate to full remote code execution, complete compromise of confidentiality, integrity, and availability of the WordPress site and underlying server.
  • Disclosure: Publicly disclosed on September 3, 2026; credited to security researcher h0xilo.

Affected software

  • Product: Divi Ajax Filter (WordPress plugin) by Divi Engine
  • Versions affected: All versions from the earliest release up to and including 5.1.2

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Divi Ajax Filter to version 5.1.3 or later. The vendor’s 5.1.3 release notes explicitly reference CVE-2026-11613 and state that custom loop templates now load only from the child theme’s templates folder, blocking unsafe/arbitrary file paths.
  • If immediate patching is not possible:
    • Disable or remove the Divi Ajax Filter plugin until the update can be applied.
    • Restrict or monitor access to plugin AJAX endpoints at the WAF/network layer, and block requests attempting to set loop_templates=custom-template with unexpected custom_loop_template values.
    • Review server logs for suspicious AJAX requests referencing template parameters, and audit the filesystem for unexpected PHP files that could be leveraged for inclusion.
  • Regularly audit all installed WordPress plugins for available security updates, since third-party plugin vulnerabilities like this remain a leading cause of WordPress site compromise.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge