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

CVE-2026-22424

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

Local File Inclusion vulnerability in the AncoraThemes Shaha PHP theme allows attackers to manipulate filename parameters in include/require statements to read arbitrary local files from the server, potentially exposing sensitive configuration files, credentials, or source code.

MitigationSanitize all input used in include/require statements by implementing strict allowlists, validating that files exist within expected directories, and avoiding direct use of user input in file path operations.

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 Shaha theme is installed
    Search the web server's document root for theme files. Check common WordPress theme directories (wp-content/themes/) or PHP application directories for a folder named 'shaha' or files containing 'shaha' in the name. Look for theme configuration files like style.css with 'Theme Name: Shaha' or theme init files.
    Affected if A folder or files named 'shaha' or 'Shaha' exists in the web application's theme or template directory.
  2. Determine the installed Shaha theme version
    Locate the main theme file (typically style.css in WordPress themes or version.php/config.php in PHP themes) within the Shaha theme directory. Open the file and look for a version declaration such as 'Version: x.x.x' or '$theme_version' variable assignment.
    Affected if The version found is 1.1.2 or lower, or if no version is explicitly declared but the theme appears to be the Shaha theme by AncoraThemes.
  3. Locate PHP files with include/require statements
    Search the Shaha theme directory for PHP files containing include, include_once, require, or require_once statements. Use a command like 'grep -r "include(" /path/to/shaha/' or examine common entry points like index.php, header.php, footer.php, and template files.
    Affected if PHP files in the theme use dynamic file inclusion with variables, such as 'include($file)' or 'require($_GET["page"])', without proper validation.
  4. Check for path traversal vulnerability patterns
    Review the include/require statements found for user-controlled input. Look for patterns where URL parameters or input variables are used directly in file paths, such as 'include($_GET["template"])' or 'include($path . "/file.php")' where $path originates from user input.
    Affected if The include/require statements accept parameters from GET/POST requests or other user-controllable sources and use them in file paths without sanitization or whitelist validation.
  5. Test for LFI if vulnerable patterns exist
    If dynamic file inclusion is found, attempt a controlled test using a known safe local file path in a non-production environment. For example, if a parameter like '?file=template' exists, try '?file=../../../../etc/passwd' (on Linux) or '?file=..\..\..\windows\system32\drivers\etc\hosts' (on Windows) to see if file contents are returned.
    Affected if The application returns contents of files outside the intended directory, confirming path traversal is possible.

The environment is affected if the Shaha theme version is 1.1.2 or lower AND the theme contains dynamic include/require statements that accept user input without sanitization, allowing path traversal attacks.

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

Sanitize all input used in include/require statements by implementing strict allowlists, validating that files exist within expected directories, and avoiding direct use of user input in file path operations.

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-22424 — 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-22424 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