Legal Stone CVE-2026-28054
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 Legal Stone legal-stone allows PHP Local File Inclusion.This issue affects Legal Stone: from n/a through <= 1.2.11.
AnalysisAI
Local file inclusion in Legal Stone WordPress theme 1.2.11 and earlier allows remote attackers to read arbitrary files and potentially execute malicious code through improper filename control in PHP include/require statements. Exploitation probability remains low (EPSS 0.15%, 36th percentile) with no confirmed active exploitation, though the network-accessible attack vector and lack of authentication requirements present material risk for sites using this theme. Patchstack database reports this vulnerability affecting all versions through 1.2.11.
Technical ContextAI
This vulnerability stems from CWE-98 (Improper Control of Filename for Include/Require Statement), a classic PHP security weakness where user-controlled input influences file paths in include(), require(), include_once(), or require_once() functions without proper validation. Legal Stone is a WordPress theme developed by ThemeREX for legal/law firm websites. The vulnerable code likely accepts user input (via GET/POST parameters, cookies, or HTTP headers) and passes it directly or with insufficient sanitization to a PHP file inclusion function. While classified as 'PHP Remote File Inclusion' in the description, the tags and Patchstack reference correctly identify this as Local File Inclusion (LFI). True RFI requires allow_url_include=On in php.ini, which is disabled by default in modern PHP. This discrepancy suggests the vulnerability primarily enables reading local server files rather than executing remote PHP payloads, though LFI can still lead to code execution via log poisoning, /proc/self/environ manipulation, or PHP filter chains.
Affected ProductsAI
WordPress theme Legal Stone by ThemeREX, all versions from initial release through version 1.2.11 inclusive. The CPE classification would follow wordpress_theme taxonomy. Patchstack vulnerability database entry at https://patchstack.com/database/Wordpress/Theme/legal-stone/vulnerability/wordpress-legal-stone-theme-1-2-11-local-file-inclusion-vulnerability confirms version 1.2.11 as the last known affected release. No specific WordPress core version dependencies are documented, though the vulnerability exists within the theme code itself rather than WordPress core.
RemediationAI
Organizations using Legal Stone theme should immediately upgrade to version 1.2.12 or later if available from ThemeREX, or consult the vendor advisory linked in Patchstack database for official patch guidance. If no patched version exists or upgrade is not immediately feasible, implement these compensating controls: disable the Legal Stone theme entirely and switch to a maintained alternative theme until patch deployment; configure web application firewall (WAF) rules to block requests containing directory traversal sequences (../, ..\ , %2e%2e%2f, encoded variants) and null bytes (%00) in query parameters and POST data targeting theme files under /wp-content/themes/legal-stone/, though this may break legitimate theme functionality requiring testing; restrict PHP open_basedir directive in php.ini or .htaccess to limit file system access to WordPress installation directory and temporary upload folders, preventing access to sensitive system files like /etc/passwd, though this requires server-level configuration access and may impact other applications. Review web server access logs for suspicious requests to Legal Stone theme endpoints containing path traversal patterns as indicators of exploitation attempts. Consult Patchstack reference at https://patchstack.com/database/Wordpress/Theme/legal-stone/vulnerability/wordpress-legal-stone-theme-1-2-11-local-file-inclusion-vulnerability for vendor-specific remediation guidance and exact patched version confirmation.
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