Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-28055: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in ThemeREX M.Williamson

0
Unknown
VulnerabilityCVE-2026-28055cvecve-2026-28055
Published: Thu Mar 05 2026 (03/05/2026, 05:54:17 UTC)
Source: CVE Database V5
Vendor/Project: ThemeREX
Product: M.Williamson

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX M.Williamson williamson allows PHP Local File Inclusion.This issue affects M.Williamson: from n/a through <= 1.2.11.

AI-Powered Analysis

AILast updated: 03/05/2026, 07:09:34 UTC

Technical Analysis

CVE-2026-28055 is a Local File Inclusion (LFI) vulnerability found in the ThemeREX M.Williamson WordPress theme, affecting all versions up to and including 1.2.11. The vulnerability stems from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to manipulate the input to include arbitrary files from the server. This can lead to the execution of malicious PHP code if an attacker can upload or access files on the server, or disclosure of sensitive information such as configuration files, password files, or other critical data. The flaw is due to insufficient input validation or sanitization, which is a common security weakness in PHP applications. Although no public exploits have been reported yet, the vulnerability is publicly disclosed and documented in the CVE database, increasing the risk of future exploitation. The affected product is a popular WordPress theme, which is widely used in various industries for website design and content management. The lack of a CVSS score indicates that the vulnerability is newly disclosed or not yet fully assessed, but the nature of LFI vulnerabilities typically allows attackers to escalate privileges or gain unauthorized access. The vulnerability does not require authentication, making it accessible to remote attackers. The absence of patch links suggests that a fix may not yet be released, so users must implement temporary mitigations or monitor for updates from ThemeREX.

Potential Impact

The impact of CVE-2026-28055 can be severe for organizations using the affected ThemeREX M.Williamson theme. Successful exploitation can lead to unauthorized disclosure of sensitive files, including configuration files containing database credentials or API keys, which can facilitate further attacks. Attackers may also execute arbitrary PHP code by including malicious files, potentially leading to full server compromise, data theft, defacement, or use of the server as a pivot point for lateral movement within a network. This can disrupt business operations, damage reputation, and result in regulatory penalties if customer data is exposed. Since WordPress powers a significant portion of the web, and themes like M.Williamson are used globally, the scope of affected systems is broad. The vulnerability's ease of exploitation without authentication increases the risk of automated scanning and mass exploitation campaigns. Organizations with public-facing websites using this theme are particularly vulnerable, including e-commerce, media, and service providers. The lack of known exploits currently provides a window for proactive mitigation before widespread attacks occur.

Mitigation Recommendations

To mitigate CVE-2026-28055, organizations should first verify if they are using the affected versions of the ThemeREX M.Williamson theme (up to 1.2.11). Immediate steps include: 1) Applying any official patches or updates released by ThemeREX as soon as they become available. 2) If no patch is available, implement manual code review and hardening by adding strict input validation and sanitization on all parameters used in include/require statements, ensuring only whitelisted filenames or paths are accepted. 3) Employ web application firewalls (WAFs) with rules to detect and block suspicious file inclusion attempts and path traversal patterns. 4) Restrict PHP file inclusion paths using open_basedir or similar PHP configuration directives to limit accessible directories. 5) Monitor web server and application logs for unusual requests that attempt to exploit file inclusion. 6) Conduct regular security assessments and penetration testing focusing on file inclusion vulnerabilities. 7) Educate development and operations teams about secure coding practices to prevent similar issues in custom themes or plugins. These measures combined can reduce the risk until a permanent fix is applied.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2026-02-25T12:13:34.839Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a9205fd1a09e29cbe6cda5

Added to database: 3/5/2026, 6:19:11 AM

Last enriched: 3/5/2026, 7:09:34 AM

Last updated: 3/5/2026, 2:46:51 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses