Kayon WordPress Theme CVE-2026-28027
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
5DescriptionCVE.org
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.
AnalysisAI
Local file inclusion in ThemeREX Kayon WordPress theme versions through 1.3 enables remote attackers to read arbitrary files from the web server filesystem and potentially execute PHP code. Despite network-reachable attack vector (CVSS AV:N), exploitation requires high complexity conditions (AC:H) without authentication, resulting in a moderate EPSS score of 0.15% (36th percentile). Patchstack database lists this as an actively tracked vulnerability affecting WordPress installations, though no CISA KEV listing indicates limited widespread exploitation at time of analysis.
Technical ContextAI
This vulnerability stems from CWE-98 (Improper Control of Filename for Include/Require Statement), commonly known as PHP file inclusion. The Kayon theme, developed by ThemeREX for WordPress, fails to properly validate or sanitize user-supplied input before passing it to PHP include/require functions. While classified as 'PHP Remote File Inclusion' in the title, Patchstack tags and technical indicators confirm this is actually a Local File Inclusion (LFI) vulnerability. LFI attacks exploit insufficient input validation in PHP file handling to access files outside the intended directory structure, typically using path traversal sequences. The affected product operates within the WordPress theming framework, where themes often dynamically load template files based on user requests or configuration parameters. The high CVSS score reflects potential for complete confidentiality, integrity, and availability compromise if an attacker chains LFI with other techniques like log poisoning or PHP wrapper exploitation to achieve code execution.
Affected ProductsAI
ThemeREX Kayon WordPress theme versions from earliest release through version 1.3 are confirmed vulnerable per Patchstack vulnerability database. This affects WordPress installations where Kayon is the active theme. The vulnerability resides in theme code rather than WordPress core, limiting exposure to sites specifically using this commercial theme product. Patchstack reference URL indicates ongoing tracking at https://patchstack.com/database/Wordpress/Theme/kayon/vulnerability/wordpress-kayon-theme-1-3-local-file-inclusion-vulnerability, though no vendor-issued security advisory from ThemeREX is referenced in available data.
RemediationAI
Upgrade Kayon theme to a version newer than 1.3 if ThemeREX has released a patched version - consult the Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/kayon/vulnerability/wordpress-kayon-theme-1-3-local-file-inclusion-vulnerability for latest patch status, as no specific fixed version number is confirmed in NVD data. If no patch exists or immediate upgrade is not feasible, implement these compensating controls: disable the Kayon theme and switch to a maintained alternative WordPress theme until patches are available (eliminates attack surface entirely but requires theme migration effort and potential design changes); restrict PHP file inclusion capabilities by setting allow_url_include=Off and open_basedir restrictions in php.ini to limit file access scope (reduces LFI impact but may break legitimate theme functionality requiring testing); implement web application firewall rules to detect and block path traversal attempts in HTTP requests targeting theme endpoints (defense-in-depth measure but can be bypassed with encoding techniques); ensure wp-config.php and other sensitive files have restrictive permissions (640 or 600) and are located outside web root where possible (limits information disclosure if LFI succeeds but doesn't prevent exploitation). Monitor WordPress access logs for suspicious patterns like '../' sequences or unexpected file parameters in theme-related requests. Note that theme switching represents the most reliable mitigation but requires visual/functional equivalence validation.
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