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.







