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

CVE-2026-22427

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 GoTravel gotravel allows PHP Local File Inclusion.This issue affects GoTravel: from n/a through <= 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 · high confidence

A PHP Local File Inclusion vulnerability exists in the Mikado-Themes GoTravel theme (versions through 2.1) where the application improperly uses user-controlled input in include/require statements. An attacker can manipulate file path parameters to include arbitrary local PHP files, potentially achieving remote code execution if they can write files to the server or access sensitive system files.

MitigationImplement strict allowlist-based validation for any file path parameters used in include/require statements, or better yet, refactor to avoid dynamic file inclusion entirely by using a mapping array of permitted includes.

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 GoTravel theme installation
    Locate the theme directory on the web server. For WordPress, check wp-content/themes/gotravel or similar. Look for theme definition files like style.css, functions.php, or theme initialization files that reference 'GoTravel' or 'Mikado' branding.
    Affected if The GoTravel theme by Mikado-Themes is present in the themes directory.
  2. Determine the installed theme version
    Open the theme's style.css file or any version metadata file within the GoTravel theme directory. Look for a 'Version:' comment or field that specifies the theme version number.
    Affected if The theme version is 2.1 or any version lower than 2.1.
  3. Find dynamic file inclusion patterns in PHP code
    Search within the GoTravel theme directory for PHP files containing include, require, include_once, or require_once statements that use superglobal variables ($_GET, $_POST, $_REQUEST) as part of the file path. Example patterns: include($_GET['file']), require($some_var).
    Affected if Any PHP file in the theme uses user-controlled input from superglobal variables in include/require statements.
  4. Identify exposed file path parameters
    Review the found inclusion code to determine which URL parameters control the file path. Test accessing those parameters via HTTP requests to confirm they are processed by the PHP code.
    Affected if The file path parameters are accessible via HTTP requests (GET or POST) without authentication or proper validation.
  5. Verify write access or sensitive file accessibility
    If the LFI is confirmed, test whether the attacker can include files they control (uploaded files) or access sensitive system files like /etc/passwd using path traversal sequences (../../../) in the vulnerable parameter.
    Affected if The application allows path traversal or includes arbitrary local files based on user input.

You are affected if the GoTravel theme version is 2.1 or lower AND your server exposes PHP files using user-supplied input in include/require statements that can be manipulated via HTTP 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

Implement strict allowlist-based validation for any file path parameters used in include/require statements, or better yet, refactor to avoid dynamic file inclusion entirely by using a mapping array of permitted includes.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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