# CVE-2026-11613: Divi Ajax Filter <= 5.1.2 - Unauthenticated Local File Inclusion via 'custom_loop_template' Parameter

> Unauthenticated attackers can achieve code execution or read sensitive data via Local File Inclusion in the Divi Ajax Filter plugin when custom templates are enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 7 Sep 2026
- **Also known as:** GHSA-57x3-7p7v-j5j4

## What is CVE-2026-11613?

CVE-2026-11613 is a critical path traversal vulnerability in Divi Ajax Filter, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 code execution in cases where .php file types can be uploaded and included. This vulnerability is only exploitable when the loop_templates parameter is set to 'custom-template'.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2026-11613?


## How do I fix CVE-2026-11613?

No fix has been published for CVE-2026-11613 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11613 being exploited?

There is no known exploitation of CVE-2026-11613 in the wild and no public exploit code.

Public exploit code:

- Divi Ajax Filter <= 5.1.2  Unauthenticated Local File Inclusion via 'custom_loop_template' (github_poc): https://github.com/Wayang1337/CVE-2026-11613

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11613 and fix it if it is affected.

What it is: CVE-2026-11613 is a critical path traversal vulnerability in Divi Ajax Filter, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11613 in the wild and no public exploit code.

Affected product: Divi Ajax Filter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11613/ (Markdown: https://insights.sbomify.com/CVE-2026-11613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11613
- OSV: https://osv.dev/vulnerability/CVE-2026-11613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11613/
Summaries are generated and may contain mistakes; the official description above is the record.