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-28060: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in ThemeREX S.King

0
Unknown
VulnerabilityCVE-2026-28060cvecve-2026-28060
Published: Thu Mar 05 2026 (03/05/2026, 05:54:18 UTC)
Source: CVE Database V5
Vendor/Project: ThemeREX
Product: S.King

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX S.King stephanie-king allows PHP Local File Inclusion.This issue affects S.King: from n/a through <= 1.5.3.

AI-Powered Analysis

AILast updated: 03/05/2026, 07:08:05 UTC

Technical Analysis

CVE-2026-28060 is a Local File Inclusion (LFI) vulnerability found in the ThemeREX S.King WordPress theme, specifically in versions up to 1.5.3. The vulnerability stems from improper control over the filename parameter used in PHP include or require statements. This allows an attacker to manipulate the input to include arbitrary files from the local server filesystem. LFI vulnerabilities can lead to information disclosure, such as reading configuration files, source code, or other sensitive data. In some cases, LFI can be leveraged for remote code execution if combined with other vulnerabilities or misconfigurations. The issue is due to insufficient input validation or sanitization, allowing attackers to traverse directories or specify unintended files. No CVSS score has been assigned yet, and no official patches or fixes have been published at the time of this report. No known exploits are currently active in the wild, but the vulnerability is publicly disclosed and documented in the CVE database. The affected product, ThemeREX S.King, is a WordPress theme used by websites that rely on this vendor for design and functionality. The vulnerability is critical for web applications that rely on this theme, as it directly impacts the confidentiality and integrity of the server environment. The attacker does not require authentication to exploit this flaw, increasing the risk profile. The vulnerability was reserved and published in early 2026, indicating recent discovery and disclosure.

Potential Impact

The impact of CVE-2026-28060 is significant for organizations using the ThemeREX S.King WordPress theme. Successful exploitation can lead to unauthorized disclosure of sensitive files, including configuration files containing database credentials, API keys, or other secrets. This compromises confidentiality and can facilitate further attacks such as privilege escalation or remote code execution if attackers find ways to inject malicious code. The integrity of the web server and hosted applications can be undermined, potentially leading to defacement or data manipulation. Availability is less directly impacted but could be affected if attackers leverage the vulnerability to disrupt services. Since the vulnerability does not require authentication and can be exploited remotely, it poses a high risk to exposed web servers. Organizations with public-facing websites using this theme are particularly vulnerable. The lack of patches increases the window of exposure. Attackers could use automated tools to scan for vulnerable sites, increasing the scale of potential attacks. The threat is relevant globally but especially critical for entities relying heavily on WordPress and ThemeREX products for their web presence.

Mitigation Recommendations

To mitigate CVE-2026-28060, organizations should immediately audit their WordPress installations to identify if the ThemeREX S.King theme version 1.5.3 or earlier is in use. Until an official patch is released, the following steps are recommended: 1) Disable or remove the vulnerable theme if it is not essential; 2) Implement strict input validation and sanitization on any user-supplied data that could influence file inclusion paths; 3) Employ web application firewalls (WAFs) with rules to detect and block suspicious file inclusion attempts, such as directory traversal patterns; 4) Restrict PHP include paths using configuration directives like open_basedir to limit accessible directories; 5) Monitor web server logs for unusual requests targeting include or require parameters; 6) Keep WordPress core, plugins, and themes updated regularly to reduce attack surface; 7) Consider deploying runtime application self-protection (RASP) solutions to detect exploitation attempts in real time; 8) Prepare an incident response plan in case exploitation is detected. Once the vendor releases a patch, apply it promptly to fully remediate the vulnerability.

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.840Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a9205fd1a09e29cbe6cdb4

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

Last enriched: 3/5/2026, 7:08:05 AM

Last updated: 3/5/2026, 3:03:41 PM

Views: 6

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