CVE-2026-22399
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 Mikado-Themes Holmes holmes allows PHP Local File Inclusion.This issue affects Holmes: from n/a through <= 1.7.
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 confidenceLocal File Inclusion (LFI) vulnerability in the Mikado-Themes Holmes WordPress theme (version <= 1.7) allows attackers to include arbitrary local PHP files due to improper control of filename parameters in include/require statements, potentially leading to 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.
-
Confirm Holmes theme installationSearch the web server for files belonging to the Holmes theme by Mikado-Themes (typically found in wp-content/themes/holmes for WordPress or similar theme directories)Affected if The Holmes theme by Mikado-Themes is present on the server
-
Locate include/require statementsSearch the theme's PHP files for include, require, include_once, or require_once statements that accept variable file paths (e.g., include($file), require($_GET['path']))Affected if Dynamic file includes using variables or user input are found in the theme code
-
Identify file path parameter sourceExamine the identified include/require calls to determine if the file path is derived from HTTP request parameters (GET/POST), cookies, or other user-controllable inputAffected if The file path passed to include/require originates from user-supplied input without validation
-
Verify allowlist absenceReview the code around the vulnerable include/require to check if an allowlist or fixed base path is used to restrict which files can be includedAffected if No input validation, allowlist, or fixed base path is implemented for the file inclusion
-
Test parameter accessibilityAttempt to access the suspected vulnerable parameter via HTTP request (e.g., ?file=../../../../etc/passwd) to confirm it reaches the vulnerable code pathAffected if The vulnerable parameter is reachable and the application processes the request
A user is affected if the Holmes theme is installed and the vulnerable include/require pattern with user-controlled file paths is present and accessible.
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 dataUpdate the Holmes theme to the latest patched version. If no patch is available, disable the theme and implement input validation with allowlist filtering on all file inclusion functions to prevent path traversal.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22399 — 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-22399 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