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

CVE-2026-22403

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 Innovio innovio allows PHP Local File Inclusion.This issue affects Innovio: from n/a through <= 1.9.

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 · high confidence

A PHP Local File Inclusion vulnerability exists in the Mikado-Themes Innovio theme (version <= 1.9) where user-supplied input is improperly used in include/require statements without sufficient validation, potentially allowing attackers to include arbitrary local files or execute malicious PHP code.

MitigationUpgrade to a patched version of the Innovio theme. If immediate patching is unavailable, implement strict input validation on all parameters used in file inclusion operations and disable allow_url_fopen/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 Innovio theme is installed
    Locate the theme directory. Common paths: wp-content/themes/innovio/ (WordPress) or the theme folder in the respective CMS. Check for the existence of style.css or theme config files containing 'Innvio' or 'Mikado Themes'.
    Affected if The Innovio theme by Mikado Themes is present on the server.
  2. Determine the installed theme version
    Open the main theme file (typically style.css, functions.php, or a version.php file) and look for a version declaration comment or variable. Compare the version number to 1.9.
    Affected if The theme version is 1.9 or lower.
  3. Identify PHP files using dynamic includes
    Search the theme directory for PHP files containing include, require, include_once, or require_once statements with variables or parameters (e.g., include($some_var), require($_GET['page']). Use grep or a code search tool to find patterns like 'include($' or 'require($_' within the theme folder.
    Affected if Dynamic include/require statements using variables or user-supplied input are found in theme PHP files.
  4. Inspect parameters used in file inclusion operations
    Review the identified include/require files. Trace the source of variables used in these statements. Check if any originate from $_GET, $_POST, or $_REQUEST superglobals without proper sanitization or validation.
    Affected if Parameters passed to include/require are derived from user input without validation.
  5. Test for LFI vulnerability (if authorized and safe)
    If you have authorization, use a low-impact test: attempt to include a known local file (e.g., ../../../../etc/passwd or the theme's own config file) via a suspected vulnerable parameter in a request to the site. Observe whether the file contents are reflected in the response.
    Affected if Arbitrary local files can be included and their contents revealed through URL parameters.

The environment is affected if the Innovio theme version is 1.9 or lower AND the theme contains PHP files with include/require statements that use unsanitized user input parameters.

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

Upgrade to a patched version of the Innovio theme. If immediate patching is unavailable, implement strict input validation on all parameters used in file inclusion operations and disable allow_url_fopen/allow_url_include in PHP configuration.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22403 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22403 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