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

0
Unknown
VulnerabilityCVE-2026-28027cvecve-2026-28027
Published: Thu Mar 05 2026 (03/05/2026, 05:54:11 UTC)
Source: CVE Database V5
Vendor/Project: ThemeREX
Product: Kayon

Description

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

AI-Powered Analysis

AILast updated: 03/05/2026, 07:22:47 UTC

Technical Analysis

CVE-2026-28027 is a Local File Inclusion (LFI) vulnerability found in the ThemeREX Kayon WordPress theme, specifically affecting versions up to 1.3. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements. This flaw allows an attacker to manipulate the input to include arbitrary files from the local filesystem, potentially leading to the execution of malicious code or disclosure of sensitive information. The vulnerability is classified as a PHP Remote File Inclusion type but technically enables Local File Inclusion, which can be leveraged for remote code execution if combined with other weaknesses or file upload capabilities. The issue was reserved in late February 2026 and published in early March 2026, with no CVSS score assigned yet and no known exploits in the wild. The lack of patch links suggests that a fix may not be publicly available at the time of reporting. Exploitation typically requires no authentication, increasing the risk profile. The vulnerability affects the Kayon theme, a product of ThemeREX, which is used by WordPress sites globally. Attackers exploiting this vulnerability can execute arbitrary PHP code, read sensitive files, or escalate privileges, potentially compromising the entire web server and connected infrastructure.

Potential Impact

The impact of CVE-2026-28027 is significant for organizations using the ThemeREX Kayon theme. Successful exploitation can lead to unauthorized disclosure of sensitive data, including configuration files, credentials, and user data. Attackers may execute arbitrary code on the affected server, leading to full system compromise, data manipulation, or service disruption. This can result in defacement, data breaches, ransomware deployment, or use of the compromised server as a pivot point for further attacks within the network. The vulnerability’s ease of exploitation without authentication increases the risk of automated attacks and widespread exploitation once public exploit code becomes available. Organizations relying on Kayon for their WordPress sites face reputational damage, regulatory penalties, and operational downtime if exploited. The threat is particularly acute for high-profile websites, e-commerce platforms, and organizations with sensitive customer data hosted on vulnerable installations.

Mitigation Recommendations

1. Immediately monitor official ThemeREX channels for security patches or updates addressing CVE-2026-28027 and apply them promptly. 2. In the absence of an official patch, implement strict input validation and sanitization on all user-controllable parameters that influence file inclusion paths to prevent manipulation. 3. Disable PHP functions that facilitate file inclusion or execution (e.g., include, require) from untrusted sources where feasible. 4. Employ Web Application Firewalls (WAFs) with rules designed to detect and block LFI attack patterns targeting the Kayon theme. 5. Restrict file system permissions to limit the web server’s access to sensitive files and directories, minimizing the impact of potential inclusion. 6. Conduct regular security audits and code reviews of customizations to the theme to identify and remediate insecure coding practices. 7. Educate site administrators on the risks and encourage immediate action upon vulnerability disclosures. 8. Consider isolating WordPress instances or using containerization to limit lateral movement in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

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

Threat ID: 69a9205ad1a09e29cbe69b3c

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

Last enriched: 3/5/2026, 7:22:47 AM

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

Views: 5

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