dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-22395

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes Fiorello fiorello allows PHP Local File Inclusion.This issue affects Fiorello: from n/a through <= 1.0.

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 confidence

A PHP Local File Inclusion (LFI) vulnerability exists in the Mikado-Themes Fiorello theme. The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file path inputs to read sensitive local files on the server. This is a high-severity issue (CVSS 8.1) requiring no authentication or user interaction to exploit.

MitigationRemediate by implementing strict input validation on all include/require statements, using whitelist-based file filtering, ensuring user-supplied filenames cannot be used directly in file inclusion functions, and disabling allow_url_include in PHP configuration.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Fiorello theme installation
    Search the web server for the Fiorello theme directory. Common paths include wp-content/themes/fiorello or themes/fiorello in the web root. List directory contents to verify the theme exists.
    Affected if The Fiorello theme by Mikado-Themes is present on the server
  2. Identify theme version
    Check the theme style.css file or theme.json file within the Fiorello theme folder for the Version header. Also check for a readme.txt or changelog file that may contain version information.
    Affected if Version cannot be determined or is within any active use range of the Fiorello theme
  3. Locate include/require statements using dynamic input
    Grep the Fiorello theme PHP files for include, require, include_once, or require_once statements that use variables or superglobals (e.g., $_GET, $_POST, $_REQUEST) without sanitization. Search for patterns like 'include($_' or 'require($_' in theme PHP files.
    Affected if Any include/require statement uses unsanitized user input (GET/POST/REQUEST parameters) as all or part of the file path
  4. Verify the vulnerable file inclusion endpoint is reachable
    Identify the PHP script containing the vulnerable include/require. Test if it can be accessed directly via HTTP without authentication. Attempt to confirm the endpoint exists and processes file path parameters.
    Affected if The vulnerable script is accessible via HTTP and accepts file path parameters without authentication
  5. Check PHP configuration for dangerous settings
    Review the php.ini or .htaccess for allow_url_include=1 and allow_url_fopen=1 settings. While this LFI is local, these settings can worsen the impact.
    Affected if allow_url_include is enabled (though primarily relevant for RFI, indicates weak PHP security posture)

The environment is affected if the Fiorello theme is installed and contains include/require statements that accept unsanitized user input for file paths, regardless of version, since no patch version range was specified.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remediate by implementing strict input validation on all include/require statements, using whitelist-based file filtering, ensuring user-supplied filenames cannot be used directly in file inclusion functions, and disabling allow_url_include in PHP configuration.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22395 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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