CVE-2026-22397
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 Fleur fleur allows PHP Local File Inclusion.This issue affects Fleur: from n/a through <= 2.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 confidenceLocal File Inclusion vulnerability in Mikado-Themes Fleur theme allows attackers to include local PHP files via unsanitized user input in include/require statements, potentially exposing sensitive system files or executing arbitrary PHP code.
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 MikadoThemes Fleur theme is installedLocate theme files by searching for 'fleur' or ' Fleur' directory names in the wp-content/themes/ folder (for WordPress) or the themes/ folder of the Mikado framework installationAffected if The Fleur theme directory exists on the server
-
Identify the installed Fleur theme versionCheck theme style.css or version.php files within the Fleur theme folder for a 'Version:' comment or $version variableAffected if The discovered version matches or predates any known vulnerable version range for this theme
-
Locate include/require statements using dynamic inputSearch PHP files in the theme for patterns like 'include($_GET', 'require($_POST', 'include($', or similar unsanitized variable usage in include/require statementsAffected if Dynamic file inclusion code using user-supplied input is found without sanitization
-
Identify the vulnerable parameter input pointsReview the identified include/require code to determine which GET/POST parameters accept file pathsAffected if Parameters like 'file', 'path', 'page', 'template', or similar are used in dynamic includes without validation
-
Verify web access to vulnerable parametersTest if the parameter endpoints are accessible via HTTP/HTTPS requests with malicious path values (e.g., ../../../../etc/passwd)Affected if The application processes the input and returns file contents or include/require behavior
-
Check for sensitive file exposureAttempt to include known system files (e.g., /etc/passwd, wp-config.php) via the identified parameters to confirm LFI existsAffected if Sensitive file contents are returned or the PHP code is executed
The environment is affected if the Fleur theme is installed, contains dynamic include/require code using unsanitized user input, and that input is accessible via web requests.
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 whitelist-based filtering for any file paths used in include/require statements; upgrade to a patched version if available from the vendor.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22397 — 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-22397 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