Skip to main content
Vulnerability Database/CVE-2026-94062

CVE-2026-94062: Werkstatt PHP File Inclusion Vulnerability

CVE-2026-94062 is a PHP local file inclusion vulnerability in Fuelthemes Werkstatt theme affecting versions through 4.8.3. Attackers can exploit improper filename controls to include malicious files. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

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-94062 Overview

CVE-2026-94062 is a PHP Local File Inclusion (LFI) vulnerability in the Fuelthemes Werkstatt WordPress theme. The flaw affects all versions of Werkstatt from unspecified initial releases through version 4.8.3. The issue stems from improper control of filename arguments passed to PHP include or require statements, classified as [CWE-98]. Attackers can abuse the vulnerable parameter to load arbitrary local PHP files from the server, which can lead to source code disclosure, configuration leakage, or code execution when combined with file upload primitives. The vulnerability is network-reachable and requires no authentication or user interaction.

Critical Impact

Unauthenticated attackers can include arbitrary local PHP files, enabling source code disclosure and potential remote code execution on WordPress sites running Werkstatt 4.8.3 or earlier.

Affected Products

  • Fuelthemes Werkstatt WordPress theme (all versions up to and including 4.8.3)
  • WordPress sites deploying the Werkstatt theme as the active parent or child theme
  • Hosting environments permitting PHP file inclusion from user-controllable input

Discovery Timeline

  • 2026-10-09 - CVE-2026-94062 published to the National Vulnerability Database
  • 2026-10-09 - Last updated in NVD database

Technical Details for CVE-2026-94062

Vulnerability Analysis

The Werkstatt theme contains a PHP file inclusion sink that accepts untrusted input and passes it to an include or require statement without adequate validation. An unauthenticated attacker crafts an HTTP request with a filename or path parameter that resolves to a server-local PHP file. The included file is then executed within the WordPress runtime context. Although classified under the broader Remote File Inclusion CWE, the practical exploitation path here is Local File Inclusion, as PHP's allow_url_include directive is typically disabled on hardened deployments. Successful exploitation exposes wp-config.php secrets, database credentials, and theme or plugin source. When paired with a secondary primitive such as log poisoning, authenticated media uploads, or session file control, LFI becomes a reliable path to arbitrary PHP execution.

Root Cause

The root cause is improper neutralization of a filename argument before it reaches a dynamic include, include_once, require, or require_once call. The theme fails to validate the parameter against an allowlist, strip directory traversal sequences such as ../, or constrain resolution to an expected template directory.

Attack Vector

The attack vector is network-based. An attacker sends a crafted HTTP request to a vulnerable Werkstatt endpoint, supplying a path parameter that references a local file. No authentication, user interaction, or prior foothold is required. The high attack complexity reflects the need to identify the exploitable parameter and construct a valid traversal payload that evades any partial filtering.

No verified public proof-of-concept code is available at the time of writing. See the Patchstack WordPress Vulnerability Advisory for technical details.

Detection Methods for CVE-2026-94062

Indicators of Compromise

  • HTTP requests to Werkstatt theme PHP endpoints containing directory traversal sequences such as ../, ..%2f, or encoded null bytes
  • Access log entries referencing sensitive local paths including wp-config.php, /etc/passwd, or /proc/self/environ
  • Unexpected PHP file reads originating from the wp-content/themes/werkstatt/ directory tree
  • New or modified PHP files in uploads directories following suspicious inclusion requests

Detection Strategies

  • Deploy web application firewall rules that flag path traversal patterns and encoded variants in query strings and POST bodies targeting theme files
  • Correlate anomalous include/require activity by monitoring PHP error logs for failed to open stream warnings referencing unexpected paths
  • Enable file integrity monitoring on WordPress core, theme, and plugin directories to detect webshell drops

Monitoring Recommendations

  • Centralize WordPress access logs and PHP error logs for retention and query across the environment
  • Alert on first-seen User-Agent and IP combinations issuing requests to Werkstatt endpoints with path parameters
  • Review outbound network connections from the web server for signs of post-exploitation command-and-control activity

How to Mitigate CVE-2026-94062

Immediate Actions Required

  • Inventory all WordPress installations and identify sites running the Werkstatt theme at version 4.8.3 or earlier
  • Apply the vendor-supplied patched release as soon as Fuelthemes publishes a fixed version
  • Restrict public access to Werkstatt theme endpoints at the web application firewall or reverse proxy layer until patched
  • Rotate WordPress secrets, database credentials, and API keys if evidence of exploitation is found

Patch Information

Fuelthemes has not published a fixed version referenced in the current advisory. Monitor the Patchstack advisory for Werkstatt and the vendor's distribution channel for an update beyond version 4.8.3. Patchstack virtual patching customers receive protection against known exploitation attempts while a vendor fix is pending.

Workarounds

  • Set the PHP directive allow_url_include = Off and confirm allow_url_fopen is disabled where not required
  • Configure open_basedir to restrict PHP file access to the WordPress document root and required temporary directories
  • Deploy WAF signatures that block directory traversal payloads and encoded variants in requests to Werkstatt theme files
  • Disable or remove the Werkstatt theme on sites that do not require it until a patched release is available
bash
# Example php.ini hardening to limit LFI blast radius
allow_url_include = Off
allow_url_fopen = Off
open_basedir = "/var/www/html:/tmp"
disable_functions = "exec,passthru,shell_exec,system,proc_open,popen"

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.