CVE-2026-28027
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA PHP Local File Inclusion vulnerability in ThemeREX Kayon theme versions up to 1.3 allows attackers to include arbitrary local files via improper input validation in include/require statements, potentially enabling remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ThemeREX Kayon theme installationCheck the theme directory for the ThemeREX Kayon theme - typically found in wp-content/themes/kayon or similar path. Look for a style.css file containing 'Theme Name: Kayon' or 'ThemeREX Kayon'Affected if ThemeREX Kayon theme is present in the WordPress themes directory
-
Determine installed theme versionOpen the theme's style.css file and locate the 'Version:' declaration in the header comment sectionAffected if The version number is 1.3 or lower, or if no version is declared and the theme appears to be the Kayon theme (it is likely vulnerable)
-
Locate dynamic include/require statementsSearch theme PHP files for patterns like 'include($_', 'require($_', 'include_once($_', 'require_once($_' - especially in files within the theme's include/ or framework/ directoriesAffected if Unsanitized dynamic includes using variables from request parameters (e.g., $_GET, $_POST, $_REQUEST) are found in theme files
-
Test parameter-based file inclusionIf vulnerable include statements are found, attempt a controlled test: access a page with a parameter that matches the vulnerable include (e.g., ?file=../../../../wp-config.php) to confirm LFI is possibleAffected if The web application returns contents of arbitrary local files when the include parameter is manipulated, indicating the LFI is exploitable
-
Check for sensitive file exposureReview if the web server has read access to sensitive files like wp-config.php, .env files, or other configuration files that may be included via the LFIAffected if The LFI can successfully read configuration or credential files outside the web root
A user is affected if the ThemeREX Kayon theme version is 1.3 or lower AND the theme contains dynamic include/require statements using unsanitized user input, which allows arbitrary local file inclusion.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on all file inclusion parameters, use allowlist validation for permitted files, and ensure include/require paths are restricted to expected directories.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28027 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28027 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data