Windsor Theme CVE-2026-28081
HIGHSeverity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX Windsor windsor allows PHP Local File Inclusion.This issue affects Windsor: from n/a through <= 2.5.0.
AnalysisAI
Local file inclusion in the ThemeREX Windsor WordPress theme allows remote attackers to include and execute arbitrary PHP files on the server through improper filename control. Affects all versions through 2.5.0. Despite CVSS 8.1 (High), EPSS indicates low exploitation probability (0.15%, 36th percentile), suggesting limited attacker interest. No active exploitation confirmed via CISA KEV at time of analysis. Patchstack database lists this vulnerability with PHP and information disclosure tags, indicating potential for data exfiltration beyond code execution.
Technical ContextAI
This is a PHP Remote/Local File Inclusion (RFI/LFI) vulnerability classified as CWE-98, occurring when user-controlled input is passed to PHP include() or require() statements without proper validation. The Windsor theme (a WordPress theme by ThemeREX) fails to sanitize file paths, allowing attackers to manipulate include/require parameters to load arbitrary local files from the server filesystem. In WordPress themes, this commonly occurs in template loaders, AJAX handlers, or custom routing functions that dynamically construct file paths. The vulnerability enables access to configuration files (wp-config.php), log files, or /etc/passwd on Linux systems, and when combined with file upload capabilities or PHP wrappers (php://filter, php://input), can escalate to remote code execution.
Affected ProductsAI
ThemeREX Windsor WordPress theme versions from earliest release through 2.5.0 are confirmed vulnerable per Patchstack advisory. This affects WordPress installations running Windsor as either active theme or inactive-but-installed theme, as some WordPress vulnerabilities can be triggered in inactive themes through direct file access. The vulnerability was reported by audit@patchstack.com and documented in the Patchstack vulnerability database under WordPress theme category. No CPE strings were provided in source data, limiting automated asset inventory matching. Site administrators can verify affected status by checking Appearance > Themes in WordPress admin panel for Windsor theme version numbers.
RemediationAI
Update ThemeREX Windsor theme to version 2.5.1 or later if available, referencing the Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/windsor/vulnerability/wordpress-windsor-theme-2-5-0-local-file-inclusion-vulnerability. If updated theme version is not yet released or update is not immediately feasible, implement these compensating controls: (1) Deactivate and delete the Windsor theme if not actively in use - WordPress can execute code in inactive themes under certain conditions. (2) Implement Web Application Firewall (WAF) rules to block requests containing directory traversal sequences (../, %2e%2e%2f) and null bytes (%00) in URL parameters targeting theme directories (/wp-content/themes/windsor/). Note this may break legitimate theme functionality if admin pages use file parameters. (3) Verify php.ini has allow_url_include=Off (default since PHP 5.2) to prevent remote file inclusion escalation, though this does not prevent local file inclusion. (4) Apply filesystem permissions limiting web server read access to sensitive files (chmod 640 on wp-config.php, restrict /etc access). Review WordPress security logs and web server access logs for suspicious requests to Windsor theme files with unusual parameters.
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
NetAlertX (formerly PiAlert) versions 23.01.14 through 24.x before 24.10.12 allow unauthenticated command injection thro
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
Same weakness CWE-98 – PHP Remote File Inclusion
View allShare
External POC / Exploit Code
Leaving vuln.today