Security readout for executives and security teams
Plain-English summary
A critical flaw in the Divi Ajax Filter WordPress plugin can let an unauthenticated internet attacker make the server load PHP files. Successful abuse could expose sensitive information, bypass access controls, disrupt the site, or execute code when a suitable PHP file is already uploadable or present. Exploitation requires the loop template setting to use “custom-template.”
Executive priority
Treat internet-facing affected sites as an immediate remediation priority because unauthenticated compromise could affect data, site integrity, and availability. First confirm plugin versions and the required custom-template configuration. Update according to current vendor guidance or disable the plugin where rapid updating is unavailable. Investigate for compromise if suspicious requests or unexpected PHP files are found.
Technical view
CVE-2026-11613 is a CWE-98 local file inclusion vulnerability affecting Divi Ajax Filter through version 5.1.2. The custom_loop_template parameter can select arbitrary PHP files for inclusion without authentication when loop_templates equals “custom-template.” Its CVSS 3.1 score is 9.8 because exploitation is network-accessible, low-complexity, requires no privileges or user interaction, and may compromise confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to WordPress installations running Divi Ajax Filter 5.1.2 or earlier with loop_templates configured as “custom-template.” Internet-accessible affected sites carry the greatest risk. The supplied evidence does not establish whether that setting is enabled by default, how many sites are exposed, or whether other controls prevent file inclusion.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and the cited information does not establish active exploitation. Attackers need network access to the vulnerable endpoint but no account or user interaction. Full code execution depends on an includable PHP file containing executable code; file inclusion may still expose data or bypass controls.
Researcher notes
The decisive precondition is loop_templates set to “custom-template”; assessments should distinguish configured exposure from simple plugin presence. The bundle describes arbitrary PHP inclusion through custom_loop_template, but provides no payload details, default-setting evidence, exploitation telemetry, or confirmed patched version. The affected metadata contains an inconsistent versions value of “0,” while the narrative explicitly states versions through 5.1.2.
Mitigation direction
- Check Divi Engine’s changelog and guidance for the current fixed release, then update promptly.
- Disable the plugin until updated if continued operation is unnecessary.
- Avoid the “custom-template” loop setting until vendor guidance confirms safe operation.
- Restrict PHP uploads and remove unauthorized PHP files from writable directories.
- Back up the site before remediation and preserve relevant logs for investigation.
Validation and detection
- Inventory WordPress sites and identify every installed Divi Ajax Filter version.
- Confirm whether loop_templates is configured as “custom-template” anywhere.
- Verify the deployed version against Divi Engine’s current security guidance and changelog.
- Review web, WordPress, and server logs for suspicious custom template requests.
- Inspect writable directories for unexpected PHP files or unauthorized file changes.
- After remediation, confirm affected routes reject unsafe template references without exposing file contents.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-98: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-11613 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/8fbb92ac-a8e7-480d-8910-416fbe902a2a?source=cveCVE reference, Wordfence
- https://diviengine.com/divi-ajax-filter-changelog/CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.