Manoir Theme CVE-2026-28019
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 Manoir manoir allows PHP Local File Inclusion.This issue affects Manoir: from n/a through <= 1.11.
AnalysisAI
Local file inclusion in the Manoir WordPress theme version 1.11 and earlier allows remote unauthenticated attackers to read arbitrary files on the server through improper validation of file inclusion parameters. Despite the high CVSS score of 8.1, EPSS data indicates low real-world exploitation probability (0.15%, 36th percentile), suggesting this is likely a targeted risk rather than widespread threat. Patchstack database confirms the vulnerability exists but no active exploitation (KEV) or public proof-of-concept has been identified at time of analysis.
Technical ContextAI
This vulnerability stems from CWE-98 (Improper Control of Filename for Include/Require Statement), commonly known as PHP file inclusion. The Manoir WordPress theme fails to properly sanitize user-controlled input before passing it to PHP include/require statements. While classified as 'PHP Remote File Inclusion' in the description, the tags and Patchstack reference confirm this is actually Local File Inclusion (LFI). In LFI attacks, the vulnerable code allows attackers to reference local server files rather than remote URLs. PHP's include/require functions interpret file paths, and without proper validation of directory traversal sequences or absolute paths, attackers can access sensitive files like wp-config.php, /etc/passwd, or other configuration files containing credentials and system information. WordPress themes are particularly susceptible when they dynamically include template files based on URL parameters or POST data without whitelist validation.
Affected ProductsAI
The vulnerability affects the Manoir WordPress theme by ThemeREX, specifically all versions from the initial release through version 1.11. CPE data is not provided in available sources. According to the Patchstack database reference at https://patchstack.com/database/Wordpress/Theme/manoir/vulnerability/wordpress-manoir-theme-1-11-local-file-inclusion-vulnerability, organizations should verify their installed version through WordPress admin dashboard under Appearance > Themes. The vulnerability exists in the theme's PHP file inclusion logic, making all installations of affected versions potentially exploitable regardless of WordPress core version, though actual exploitation depends on specific theme feature usage and configuration.
RemediationAI
ThemeREX should be contacted immediately for patch availability, as no specific fix version is confirmed in current intelligence sources. Organizations running Manoir theme version 1.11 or earlier should check the official ThemeREX website and WordPress theme repository for updates beyond version 1.11. Consult the Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/manoir/vulnerability/wordpress-manoir-theme-1-11-local-file-inclusion-vulnerability for vendor response and patch timeline. If no patched version is available, implement compensating controls: restrict access to WordPress admin dashboard using IP whitelisting at web server or WAF level to prevent unauthorized theme exploitation; disable the Manoir theme entirely and switch to a maintained alternative if critical features are not required; deploy web application firewall rules to block requests containing directory traversal sequences (../, ../../, %2e%2e%2f) and common LFI payloads targeting theme directories. Note that WAF rules may cause false positives with legitimate file upload features. Monitor WordPress access logs for suspicious requests to theme files with file path parameters. These mitigations reduce but do not eliminate risk; theme replacement or vendor patch remains the only complete solution.
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