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

CVE-2026-22413

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 Malgré malgre allows PHP Local File Inclusion.This issue affects Malgré: from n/a through <= 1.0.3.

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 vulnerability exists in the Mikado-Themes Despite theme (versions through 1.0.3). The vulnerability stems from improper control of filenames used in include/require statements, allowing attackers to include arbitrary local PHP files by manipulating input parameters.

MitigationUpdate the theme to the latest patched version if available. If no patch exists, disable or remove the theme. Additionally, configure PHP to disable allow_url_include and implement proper input validation on all file include paths.

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. Identify if Mikado-Themes Despite theme is installed
    Locate the theme directory on the web server. The theme is typically found in wp-content/themes/despite (for WordPress) or in the themes folder of the respective CMS. Search for files containing 'Despite' or 'mikado' in the theme name.
    Affected if The Despite theme directory exists on the server and is actively in use.
  2. Determine the installed theme version
    Open the theme's style.css file or version.php file within the theme directory and locate the version declaration. Compare this version number to the affected range (versions through 1.0.3).
    Affected if The installed version is 1.0.3 or any earlier version of the theme.
  3. Locate file inclusion code in the theme
    Search the theme directory for PHP files containing include, require, include_once, or require_once statements that use variables or parameters without proper sanitization. Look for patterns like 'include($var)', 'require($_GET[...])', or similar dynamic file inclusion.
    Affected if Dynamic file inclusion code using unsanitized user input is present in any PHP file within the theme.
  4. Identify vulnerable input parameters
    Examine the file inclusion code found in the previous step. Identify which GET, POST, or REQUEST parameters are used in the include/require statements. Test if these parameters accept arbitrary file paths (e.g., ../../../../etc/passwd).
    Affected if The identified parameters allow traversal sequences or direct file paths to be included from the local filesystem.
  5. Check for input validation on file include paths
    Review the PHP code around the include/require statements to determine if any whitelist validation, basename(), or path sanitization is applied to the input before use in file inclusion.
    Affected if No input validation, whitelist filtering, or path sanitization exists on the parameters used in file inclusion.

The environment is affected if the Despite theme version 1.0.3 or earlier is installed AND dynamic file inclusion code using unsanitized input parameters exists in the theme's PHP files.

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

Update the theme to the latest patched version if available. If no patch exists, disable or remove the theme. Additionally, configure PHP to disable allow_url_include and implement proper input validation on all file include paths.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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