CVE-2026-28011: 
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-28011 is a Local File Inclusion (LFI) vulnerability in the ThemeREX Yottis WordPress theme, classified under CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program). It affects all versions of the Yottis theme up to and including version 1.0.10, and can be exploited by unauthenticated remote attackers. The vulnerability was reported by researcher 'Bonds' on October 4, 2025, and published by Patchstack on March 2, 2026. It carries a CVSS v3.1 base score of 8.1 (High) (Patchstack).

Technical details

The vulnerability stems from improper validation of filenames used in PHP include/require statements within the Yottis theme (CWE-98), allowing an attacker to manipulate file path parameters to include arbitrary local files on the server. This is a network-based attack with high complexity, requiring no authentication or user interaction, and maps to CAPEC-193 (PHP Remote File Inclusion). An attacker can craft a malicious HTTP request that causes the PHP interpreter to include and potentially execute local files outside the intended scope. No public proof-of-concept code has been disclosed at this time (Patchstack, Feedly).

Impact

Successful exploitation allows a remote, unauthenticated attacker to read sensitive local files — such as WordPress configuration files (wp-config.php) containing database credentials — and potentially execute arbitrary PHP code with the privileges of the web server process. This can lead to full database compromise, exposure of user data, and complete takeover of the affected WordPress installation. The integrity and availability of the web application are also at high risk, as attackers could modify or destroy data following initial access (Patchstack).

Exploitability

No public proof-of-concept exploit or active in-the-wild exploitation has been reported as of the time of publication. The EPSS score is approximately 0.053%, indicating a low but non-negligible probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Patchstack notes that vulnerabilities of this class (LFI with CVSS 8.1) are frequently used in mass-exploit campaigns targeting WordPress sites regardless of their traffic or popularity (Patchstack, Feedly).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites using the Yottis theme (version ≤ 1.0.10) via passive scanning tools (e.g., WPScan, Shodan) or by inspecting page source for theme references such as /wp-content/themes/yottis/.
  2. Identify vulnerable parameter: Locate the theme's PHP file(s) that accept user-controlled input for file inclusion (e.g., a template, file, or page parameter in a theme component or AJAX handler).
  3. Craft malicious request: Send an HTTP GET or POST request with a manipulated file path parameter, such as ?file=../../../../wp-config.php or similar path traversal sequences, targeting the vulnerable endpoint.
  4. Extract sensitive data: Review the server response for the contents of included files — particularly wp-config.php for database credentials, salts, and keys.
  5. Escalate access: Use obtained credentials to access the WordPress database directly, authenticate to the WordPress admin panel, or chain with other vulnerabilities for remote code execution (Patchstack).

Indicators of compromise

  • Network: Unusual HTTP requests to WordPress theme endpoints containing path traversal sequences (e.g., ../, ..%2F, %2e%2e%2f) in query parameters; repeated requests to theme PHP files from a single IP.
  • Logs: Web server access logs showing requests with file path parameters pointing to sensitive files (e.g., wp-config.php, /etc/passwd); PHP error logs indicating failed or successful file inclusion of unexpected paths.
  • File System: Unexpected new PHP files or web shells in the /wp-content/themes/yottis/ directory; modification timestamps on theme files that do not align with legitimate updates.
  • Process: Unusual child processes spawned by the web server (e.g., bash, curl, wget) following HTTP requests to theme endpoints.

Mitigation and workarounds

No official patch from ThemeREX is available for Yottis version 1.0.10 or earlier as of the publication date. Site owners should remove or replace the Yottis theme until a patched version is released. Patchstack has issued a virtual patch (mitigation rule) for its subscribers to block exploitation attempts in the interim. Additional hardening steps include: disabling allow_url_include and allow_url_fopen in php.ini, deploying a Web Application Firewall (WAF) with rules targeting LFI patterns, applying least-privilege file system permissions to the web server user, and monitoring application logs for suspicious file inclusion patterns (Patchstack).

Community reactions

The vulnerability was assigned and disclosed by Patchstack, which classified it as high priority and noted its potential for use in mass-exploit campaigns. No significant vendor statements from ThemeREX or broader media coverage have been identified at this time.

Additional resources


Source: This report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-86850MEDIUM6.5
  • sku-error-fixer-for-woocommerce
NoNoOct 06, 2026
CVE-2026-88931MEDIUM5.3
  • social-web-suite
NoNoOct 06, 2026
CVE-2026-87841MEDIUM5.3
  • unitechpay-paiements-mobile-money
NoNoOct 06, 2026
CVE-2026-92990MEDIUM5.3
  • sendpress
NoNoOct 06, 2026
CVE-2026-92989MEDIUM4.3
  • sendpress
NoNoOct 06, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management