CVE-2026-125795 in Estatik Plugin
Summary
by MITRE • 11/15/2026
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Estatik Estatik estatik allows PHP Local File Inclusion.This issue affects Estatik: from n/a through 4.3.6.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/15/2026
The security flaw identified within the Estatik plugin, specifically affecting versions ranging from its initial release up to version 4.3.6, represents a critical failure in input validation and file handling mechanisms inherent to PHP applications. This vulnerability is categorized under the broader class of Improper Control of Filename for Include or Require Statement, commonly known as Remote File Inclusion or Local File Inclusion depending on whether an external URL or local path is exploited. The core technical issue stems from the application's failure to adequately sanitize user-supplied input before utilizing it in PHP functions such as include(), require(), include_once(), or require_once(). When a developer constructs these statements using dynamic variables derived directly from HTTP requests without rigorous validation, they create an execution pathway that allows attackers to dictate which script files are loaded into the current process context. This lack of strict whitelisting for allowed file paths constitutes a fundamental architectural weakness in the software's design phase.
From a technical perspective, this vulnerability enables two distinct but related attack vectors depending on server configuration and attacker capability. In cases where PHP allows remote includes via the allow_url_include directive being enabled, an attacker can supply a malicious URL as input. The vulnerable script then fetches and executes arbitrary code hosted on an external server controlled by the adversary. This scenario aligns with CWE-98 Improper Control of Filename for Include Statement in the Common Weakness Enumeration taxonomy. If remote includes are disabled but local file paths are still manipulated, the attacker may exploit path traversal sequences to include sensitive system files or locally stored malicious scripts, which falls under CWE-22 Path Traversal and potentially CWE-434 Unrestricted Upload of File with Dangerous Type if combined with upload vulnerabilities. The presence of this flaw indicates that the application does not enforce strict boundaries on file inclusion operations, allowing external influence over internal logic flow.
The operational impact of exploiting this vulnerability is severe and often leads to complete system compromise. By successfully injecting malicious code through the include or require mechanism, an attacker can achieve arbitrary remote code execution on the web server hosting the Estatik application. This capability allows for a wide range of destructive actions including but not limited to defacement of the website, theft of sensitive data such as user credentials and database contents, installation of backdoors for persistent access, and using the compromised server as a pivot point for further attacks against internal network resources. The severity is compounded by the fact that many WordPress plugins operate with web server privileges, meaning successful exploitation grants the attacker full control over the underlying operating system environment accessible to the web process. This aligns with MITRE ATT&CK technique T1059 Command and Scripting Interpreter, specifically PHP scripting, as well as T1190 Exploit Public-Facing Application, highlighting how this flaw serves as a primary entry point for automated exploitation campaigns targeting vulnerable WordPress installations.
Mitigation strategies must address both immediate remediation and long-term defensive posture improvements. The most effective solution is to upgrade the Estatik plugin to version 4.3.7 or later where these input validation issues have been resolved by developers implementing strict whitelisting of allowed file paths rather than relying on blacklist approaches which are prone to bypasses. For organizations unable to patch immediately, disabling PHP remote includes via server configuration settings such as setting allow_url_include to Off in php.ini provides a critical layer of defense against the most common exploitation vector. Additionally, administrators should ensure that error reporting is disabled in production environments to prevent information leakage that could aid attackers in crafting precise path traversal payloads. Implementing Web Application Firewalls with rules specifically designed to detect and block suspicious include patterns or encoded characters commonly used in file inclusion attacks can also serve as an effective compensating control while patching efforts are underway.