CVE-2026-22387
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 Aviana aviana allows PHP Local File Inclusion.This issue affects Aviana: from n/a through <= 2.1.
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 Mikado-Themes Aviana theme (versions through 2.1) contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without adequate validation. This allows attackers to include arbitrary local files, potentially leading to remote code execution if they can control included 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
- 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 Aviana theme installationSearch the web server themes directory (commonly wp-content/themes or /themes) for a folder named 'aviana' or containing 'mikado' branding. Look for a style.css file with 'Aviana' or 'Theme Name: Aviana' in the comment header.Affected if The Mikado-Themes Aviana theme is installed on the server.
-
Determine the installed theme versionOpen the theme's style.css file and locate the 'Version:' field in the header comment block. Compare this version number to 2.1 (versions 2.1 and below are affected).Affected if The theme version is 2.1 or lower.
-
Find PHP include/require with user inputUse grep or a file search tool to scan PHP files in the theme directory for patterns like 'include($', 'require($', 'include_once($', 'require_once($' combined with superglobal variables such as $_GET, $_POST, $_REQUEST, or $_COOKIE.Affected if The theme contains PHP include or require statements that use parameters derived from user input.
-
Inspect the vulnerable parameter usageExamine each identified include/require call. Check whether the user-supplied parameter is used directly in the file path without sanitization, whitelisting, or validation logic.Affected if User-supplied parameters are used directly in include/require statements without input validation or file whitelisting.
-
Confirm accessibility of vulnerable endpointsReview the PHP files containing the vulnerable includes to determine if they are accessible via web requests without authentication. Check if the code is in publicly reachable PHP files.Affected if The vulnerable code is reachable by unauthenticated users through web requests.
Your environment is affected if the Aviana theme version is 2.1 or lower and contains PHP include/require statements that use unsanitized user input from parameters 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 dataImplement strict input validation and whitelisting on all parameters used in include/require statements, ensuring only predefined/allowed files can be included. Replace dynamic includes with hardcoded includes or use a whitelist approach for any dynamic file inclusion.
- 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-22387 — 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-22387 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