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

CVE-2026-22374

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 Zio Alberto zioalberto allows PHP Local File Inclusion.This issue affects Zio Alberto: 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 · high confidence

A PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Zio Alberto WordPress theme (versions through 1.2.2) allows attackers to manipulate include/require statements to execute arbitrary PHP code from local files. The improper control of filenames enables reading sensitive files or achieving remote code execution when combined with file upload or log poisoning techniques.

MitigationUpgrade to a patched version of the Zio Alberto theme; if no patch is available, remove or replace the theme entirely. Implement strict input validation on include/require paths and disable allow_url_include in PHP configuration.

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. Confirm Zio Alberto theme is installed
    Navigate to wp-content/themes/ directory or check via WordPress admin under Appearance > Themes. Look for a theme folder named 'zio-alberto' or similar.
    Affected if The Zio Alberto theme by AncoraThemes is present in the WordPress themes directory.
  2. Identify the installed theme version
    Open the style.css file within the theme folder (wp-content/themes/zio-alberto/style.css) and look for the 'Version:' header in the file comments.
    Affected if The version listed is 1.2.2 or lower (versions through 1.2.2 are affected per the CVE).
  3. Locate vulnerable include/require code
    Search the theme files for dynamic include/require statements that use unsanitized variables, such as: include($_GET['template']), require($theme_path.'/header.php'), or similar patterns where user input directly controls the include path.
    Affected if PHP files in the theme contain include, require, include_once, or require_once statements that incorporate raw $_GET, $_POST, or other user-controlled input into the file path.
  4. Check for publicly accessible parameter entry points
    Review PHP files identified in step 3 to determine if the vulnerable parameters are passed via URL GET parameters (e.g., ?page=template) and are accessible without authentication.
    Affected if The vulnerable code paths can be reached via HTTP requests without requiring logged-in status or admin privileges.
  5. Inspect server-side file access permissions
    Verify that the web server user (e.g., www-data, apache) has read access to sensitive files like /etc/passwd, wp-config.php, or other configuration files that could be targeted for LFI.
    Affected if The web server process has read permissions on system files or WordPress configuration files that could be included via the LFI vulnerability.

The environment is affected if the Zio Alberto theme version is 1.2.2 or lower AND the theme contains dynamic include/require statements using unsanitized user input that are accessible via HTTP requests.

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 Zio Alberto theme; if no patch is available, remove or replace the theme entirely. Implement strict input validation on include/require paths and disable allow_url_include in PHP configuration.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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