CVE-2026-57795
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 themelexus Kitchor kitchor allows PHP Local File Inclusion.This issue affects Kitchor: from n/a through <= 1.4.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 confidenceThe themelexus Kitchor theme versions 1.4.3 and below contain a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without sufficient validation. An attacker can manipulate filename parameters to include arbitrary local PHP files, potentially achieving remote code execution if they can upload files or access sensitive system files.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Kitchor theme versionLocate the theme's style.css file typically at wp-content/themes/kitchor/style.css or check the theme's version.php file and note the declared version numberAffected if The installed version is 1.4.3 or lower
-
Locate dynamic file inclusion codeSearch the theme's PHP files for include, require, include_once, or require_once statements that reference $_GET, $_POST, $_REQUEST, or similar user-supplied parameters without sanitizationAffected if Any include/require statement uses unsanitized user input to construct file paths
-
Identify the vulnerable filename parameterExamine the identified inclusion code to find which specific parameter (commonly 'filename', 'file', 'page', 'template', or similar) controls the included file pathAffected if The parameter used in the include/require is directly passed from user input without validation or allowlisting
-
Verify parameter accessibilityCheck whether the vulnerable code path is accessible to unauthenticated users by examining function wrappers, authentication checks, and the request method required to trigger the inclusionAffected if The file inclusion functionality can be triggered by unauthenticated users or without proper access controls
Your environment is affected if the Kitchor theme version is 1.4.3 or lower AND the theme contains include/require statements using unvalidated user-supplied filename parameters that are accessible to attackers.
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 dataAudit and sanitize all include/require statements to use allowlisted file paths, implement strict input validation, and consider removing dynamic file inclusion functionality if not essential. Upgrade to any available patched version.
- 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-57795 — 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-57795 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