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

CVE-2026-22364

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 axiomthemes SevenTrees seventrees allows PHP Local File Inclusion.This issue affects SevenTrees: from n/a through <=1.0.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 PHP Local File Inclusion vulnerability in the axiomthemes SevenTrees theme allows attackers to include arbitrary local files via improper control of filename parameters in include/require statements. This can enable unauthorized reading of sensitive system files.

MitigationAudit and sanitize all file inclusion operations (include, require, include_once, require_once) to use whitelisted file paths or validated input; update to the latest theme version if a patch is 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. Locate the SevenTrees theme installation
    Search your web server document root for the 'seventrees' or 'SevenTrees' directory, typically found in wp-content/themes/ (WordPress) or similar theme directories for other PHP applications.
    Affected if The SevenTrees theme by axiomthemes is installed in the web accessible directory.
  2. Identify the theme version
    Check for a style.css, info.txt, or theme.json file within the SevenTrees theme folder and look for a Version: or similar version declaration in the header comments or metadata.
    Affected if The theme version cannot be determined or is older than the latest patched version from axiomthemes.
  3. Search for unsafe file inclusion patterns
    Use grep or a text search to find include, require, include_once, or require_once statements in PHP files within the theme folder. Look for patterns where variable parameters like $_GET, $_POST, or $_REQUEST are used directly in the include/require path without sanitization (e.g., include($_GET['file']);).
    Affected if Any PHP file in the theme contains include/require statements that use unsanitized user input (GET, POST, REQUEST parameters) to construct file paths.
  4. Identify the vulnerable parameter entry points
    Examine the identified vulnerable include/require code and determine which URL parameters control the file inclusion. Check if these parameters are accessible via HTTP requests to the affected PHP scripts.
    Affected if The vulnerable file inclusion code can be reached via HTTP requests with user-controllable filename parameters.
  5. Review access controls on affected PHP files
    Check the directory where vulnerable PHP files reside for .htaccess restrictions or authentication requirements that might limit access to the vulnerable scripts.
    Affected if The vulnerable file inclusion endpoints are directly accessible to unauthenticated users without additional access controls.

Your environment is affected if the SevenTrees theme by axiomthemes is installed and contains PHP files with include/require statements that use unsanitized user input to construct file paths, which are accessible to remote attackers.

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

Audit and sanitize all file inclusion operations (include, require, include_once, require_once) to use whitelisted file paths or validated input; update to the latest theme version if a patch is available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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