Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-94067 Overview
CVE-2026-94067 is a Local File Inclusion (LFI) vulnerability in the Fuelthemes The Voux WordPress theme (thevoux-wp). The flaw stems from improper control of filenames in PHP include or require statements [CWE-98]. Attackers can abuse this weakness over the network without authentication or user interaction. The vulnerability affects all versions of The Voux from an unspecified initial release through version 6.9.5. Successful exploitation allows adversaries to include arbitrary local files, potentially leading to source code disclosure, sensitive configuration leaks, and remote code execution when combined with file upload primitives.
Critical Impact
Unauthenticated attackers can include arbitrary local PHP files through the vulnerable theme, enabling information disclosure and code execution on affected WordPress sites.
Affected Products
- Fuelthemes The Voux WordPress theme (thevoux-wp) versions up to and including 6.9.5
- WordPress installations running the affected theme on any PHP version
- Shared hosting environments with multiple WordPress sites using The Voux
Discovery Timeline
- 2026-10-09 - CVE CVE-2026-94067 published to NVD
- 2026-10-09 - Last updated in NVD database
Technical Details for CVE-2026-94067
Vulnerability Analysis
The vulnerability belongs to the PHP File Inclusion class of flaws tracked under [CWE-98]. The Voux theme passes attacker-controlled input into a PHP include or require statement without sufficient validation. Although the CWE identifier references Remote File Inclusion, the Patchstack advisory confirms exploitation is limited to Local File Inclusion in this instance.
An attacker can request a crafted URL that resolves to a sensitive server-side file. Typical targets include wp-config.php, log files containing injected PHP, and session files. On misconfigured hosts, chaining LFI with log poisoning or uploaded media can escalate to arbitrary code execution.
The exploit requires high attack complexity, likely due to filename normalization or path constraints inside the theme. However, no privileges or user interaction are needed, and impact extends to confidentiality, integrity, and availability.
Root Cause
The root cause is improper sanitization of a filename parameter passed to a dynamic PHP inclusion function. The theme accepts user-supplied data through an HTTP request parameter and concatenates it into an include() or require() call without allowlisting valid paths or stripping traversal sequences such as ../.
Attack Vector
Exploitation occurs over the network against the WordPress HTTP endpoint exposing the vulnerable theme functionality. An unauthenticated attacker sends a crafted request with a manipulated filename parameter. The server resolves the path and executes or discloses the included file. For technical reproduction details, refer to the Patchstack Vulnerability Report.
Detection Methods for CVE-2026-94067
Indicators of Compromise
- HTTP requests to The Voux theme endpoints containing path traversal sequences such as ../, ..%2f, or encoded null bytes
- Access log entries referencing sensitive files like wp-config.php, /etc/passwd, or /proc/self/environ
- Unexpected PHP processes spawned from the web server user following suspicious theme requests
- New or modified PHP files inside wp-content/uploads/ with web-executable content
Detection Strategies
- Deploy web application firewall rules that block path traversal patterns in query parameters targeting /wp-content/themes/thevoux-wp/ paths
- Enable PHP open_basedir restrictions and monitor error logs for open_basedir restriction in effect warnings tied to theme files
- Hunt in HTTP access logs for requests that combine theme parameters with filesystem paths or encoded traversal strings
Monitoring Recommendations
- Monitor file integrity on wp-config.php, theme directories, and plugin directories for unexpected reads or modifications
- Alert on outbound connections from the web server process to unusual destinations, which may indicate post-exploitation activity
- Track WordPress audit logs for theme and plugin changes alongside anomalous administrator session activity
How to Mitigate CVE-2026-94067
Immediate Actions Required
- Identify all WordPress sites running The Voux theme and confirm the installed version against the vulnerable range through 6.9.5
- Apply the vendor-supplied security update as soon as it is available from Fuelthemes or the WordPress theme repository
- Place a web application firewall rule in front of affected sites to block traversal payloads and known LFI patterns targeting The Voux
- Rotate secrets stored in wp-config.php, including database credentials and authentication keys, if exploitation is suspected
Patch Information
Fuelthemes has published a vulnerability record through Patchstack. Site administrators should upgrade to a version of The Voux later than 6.9.5 once released. Review the Patchstack Vulnerability Report for the latest fixed version and vendor guidance.
Workarounds
- Disable or remove The Voux theme until a patched version is installed, switching to a maintained alternative
- Configure PHP open_basedir and disable_functions to limit file access scope for the web server user
- Enforce least-privilege filesystem permissions so that the web server account cannot read wp-config.php outside required operations
- Deploy a managed WAF with virtual patching for WordPress LFI patterns targeting theme parameters
# Example WAF rule concept (ModSecurity) to block traversal in theme requests
SecRule REQUEST_URI "@contains /wp-content/themes/thevoux-wp/" \
"id:1009406,phase:2,deny,status:403,log,\
chain,msg:'CVE-2026-94067 LFI attempt against The Voux theme'"
SecRule ARGS "@rx (\.\./|\.\.%2f|%00|/etc/passwd|wp-config\.php)" "t:lowercase,t:urlDecodeUni"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

