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

CVE-2026-22431

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 Wabi-Sabi wabi-sabi allows PHP Local File Inclusion.This issue affects Wabi-Sabi: 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 · high confidence

The Wabi-Sabi theme by AncoraThemes contains a PHP Local File Inclusion (LFI) vulnerability where user-controlled input is used in include/require statements without proper validation. This allows attackers to include arbitrary local files, potentially leading to sensitive data disclosure or remote code execution if they can upload malicious PHP files or leverage the inclusion to execute existing code on the server.

MitigationImplement strict input validation using allowlists for permitted files, replace dynamic file inclusion with a switch/case or mapping approach, and consider deploying a Web Application Firewall as a temporary protective measure until the code-level fix is applied.

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 Wabi-Sabi theme files
    Search the web server document root for directories named 'wabi-sabi', 'Wabi-Sabi', or similar case variations. Check wp-content/themes/ for WordPress implementations or the themes/ directory for other PHP applications.
    Affected if The Wabi-Sabi theme by AncoraThemes is present on the server
  2. Determine the theme version
    Open the theme's style.css file (typically in the theme root) and look for the 'Version:' header in the CSS comment block at the top. Alternatively, check theme.json or any version.php file within the theme directory.
    Affected if Any version of the Wabi-Sabi theme by AncoraThemes is installed (no version range was specified for this CVE)
  3. Identify dynamic file inclusion patterns
    Search the theme's PHP files for include, include_once, require, or require_once statements that use variables from $_GET, $_POST, $_REQUEST, or similar superglobals as the file path (e.g., include($_GET['file']); or require($theme_dir . $_REQUEST['template']);).
    Affected if Any PHP file in the theme contains include/require statements using unsanitized user input from superglobals
  4. Inspect the vulnerable parameter usage
    Examine any identified include/require statements for the specific parameter names being used (common examples include 'file', 'page', 'template', 'path', 'dir'). Verify whether these parameters accept arbitrary file paths without validation.
    Affected if The theme accepts file paths through URL parameters (GET/POST) without allowlist validation or sanitization
  5. Verify if arbitrary file reading is possible
    Test the suspected parameter by submitting a benign file path such as ../../wp-config.php (for WordPress) or ../../../etc/passwd to see if the file contents are returned in the response. Use a controlled request to confirm the LFI behavior.
    Affected if The server returns the contents of files outside the intended theme directory when requesting them via the vulnerable parameter

You are affected if the Wabi-Sabi theme by AncoraThemes is installed AND your server returns file contents when supplying file paths through URL parameters to the theme's PHP files, indicating unrestricted file inclusion is possible.

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 using allowlists for permitted files, replace dynamic file inclusion with a switch/case or mapping approach, and consider deploying a Web Application Firewall as a temporary protective measure until the code-level fix is applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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