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

CVE-2026-22371

HIGH · 8.1 CVSS v3.1 Published 2026-02-20
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 AncoraThemes Gustavo gustavo allows PHP Local File Inclusion.This issue affects Gustavo: from n/a through <= 1.2.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

This is a Local File Inclusion (LFI) vulnerability in the AncoraThemes Gustavo WordPress theme (versions <= 1.2.2). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate input parameters to include arbitrary PHP files from the server, potentially leading to remote code execution.

MitigationUpgrade to a patched version of the Gustavo theme. If no patch is available, implement strict input validation with whitelist-based filtering on all parameters used in include/require statements, and ensure PHP allow_url_include is disabled.

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 Gustavo theme installation
    Locate the theme directory on your web server. The Gustavo theme by AncoraThemes is typically found in wp-content/themes/gustavo or similar theme directories depending on the CMS. Check for the presence of theme files including style.css and functions.php.
    Affected if The Gustavo theme directory exists on the server and contains theme files.
  2. Determine installed theme version
    Open the theme's style.css file and look for the 'Version:' declaration in the file header comment. Compare this version number to the affected range (version 1.2.2 and below).
    Affected if The installed version is 1.2.2 or lower.
  3. Locate include/require statements using user input
    Search the theme's PHP files (especially functions.php, header.php, footer.php, and any template files) for include, include_once, require, or require_once statements that use variables derived from $_GET, $_POST, $_REQUEST, or $_COOKIE superglobals as the path argument.
    Affected if PHP files contain include/require statements that directly or indirectly use unsanitized user input as the file path.
  4. Check for vulnerable parameter handling
    Examine how request parameters are processed in the theme. Look for patterns where parameters like 'template', 'page', 'file', 'path', 'slug', or similar are used to construct file paths without proper validation (such as checking for directory traversal sequences like '../' or restricting to allowed directories).
    Affected if The theme accepts request parameters that control file inclusion without validating that the path stays within an expected directory.
  5. Verify if the vulnerable code is reachable
    Test whether the affected include/require code paths can be triggered by making HTTP requests with manipulated parameters. For WordPress themes, this may involve accessing specific template files or theme functions directly.
    Affected if The vulnerable code path is accessible via web request and accepts user-supplied input that can be manipulated to traverse directories.

You are affected if the Gustavo theme version is 1.2.2 or lower AND your server has PHP code that uses unsanitized user input in include/require statements, which can be triggered through web requests to read arbitrary 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

Upgrade to a patched version of the Gustavo theme. If no patch is available, implement strict input validation with whitelist-based filtering on all parameters used in include/require statements, and ensure PHP allow_url_include is disabled.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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