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

CVE-2026-22414

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

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 Local File Inclusion (LFI) vulnerability in the Mikado-Themes Marra theme allows attackers to manipulate PHP include/require statements by injecting malicious file paths through unsanitized input, potentially leading to arbitrary PHP code execution on the server.

MitigationImplement strict input validation with allowlist validation for any file paths used in include/require statements, disable allow_url_fopen and allow_url_include in php.ini, and update to a patched version if available.

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 the Marra theme is installed
    Locate the theme directory - typically in wp-content/themes/marra/ for WordPress or similar theme folder for the CMS in use. Check for a style.css or theme.json file that declares the theme name as 'Marra' by Mikado-Themes.
    Affected if The Marra theme by Mikado-Themes is present in the themes directory.
  2. Determine the installed Marra theme version
    Open the theme's style.css file (or theme.json) and look for the 'Version:' header in the theme comments. Compare this version number against any known affected version ranges for CVE-2026-22414.
    Affected if The theme version matches or falls within an affected version range for this LFI vulnerability.
  3. Search for vulnerable include/require patterns
    In the theme directory, search PHP files for patterns like 'include($_', 'require($_', 'include_once($_', 'require_once($_' where user input (GET, POST, REQUEST parameters) flows directly into these statements without apparent sanitization.
    Affected if PHP files in the theme contain include/require statements that use unsanitized variables from user input.
  4. Verify user input reaches file inclusion functions
    Trace the variable used in the include/require statement back to its source. Check if it originates from $_GET, $_POST, $_REQUEST, or other user-controllable input without validation via functions like basename(), pathinfo(), or allowlist checks.
    Affected if User-supplied input from request parameters flows into include/require without validation.
  5. Check for the specific vulnerable code location
    Examine common entry points in the theme (index.php, header.php, template files) for file inclusion logic that accepts a parameter (often named 'template', 'page', 'file', or similar) and passes it to include/require. Look for code that concatenates or directly uses this parameter in file paths.
    Affected if The theme contains code that dynamically includes files based on user-supplied parameters without proper path validation.

You are affected if the Marra theme is installed and contains PHP code that passes unsanitized user input directly into include or require statements, allowing path manipulation.

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

Implement strict input validation with allowlist validation for any file paths used in include/require statements, disable allow_url_fopen and allow_url_include in php.ini, and update to a patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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