CVE-2026-22377
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Saveo saveo allows PHP Local File Inclusion.This issue affects Saveo: 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 · moderate confidenceLocal File Inclusion vulnerability in AncoraThemes Saveo theme (versions <= 1.1.2) where improper control of filenames in PHP include/require statements allows attackers to include arbitrary local PHP files. This is a code-level vulnerability in the theme's PHP code where user-controlled input is passed to include/require statements without proper sanitization.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Saveo theme versionLocate the theme's version identifier: check the style.css file header in wp-content/themes/saveo/ for the 'Version:' comment, or if using a modern block theme, check theme.json in the same directory. Compare the found version to the affected range (<= 1.1.2).Affected if The installed version is 1.1.2 or lower.
-
Confirm vulnerable include/require patterns existSearch the theme's PHP files (particularly in the main theme directory and any subdirectories like inc/, includes/, or template-parts/) for include, include_once, require, or require_once statements that reference variables without sanitization. Look for patterns such as 'include($', 'require($', or similar where user-supplied parameters might flow into these calls.Affected if PHP files contain include/require statements using unsanitized variable input that could be controlled by an attacker.
-
Identify entry points for user inputReview the theme's PHP files for parameters from superglobals ($_GET, $_POST, $_REQUEST) being used directly in include/require paths without validation. Check functions.php and any template files that handle routing or dynamic content loading.Affected if User-controllable parameters are passed to include/require statements without allowlist validation or path restriction.
-
Verify web server access to敏感 filesConfirm the web server process has read access to system files outside the web root (such as /etc/passwd, configuration files, or other PHP files) that could be targeted via the LFI vector.Affected if The web server user can read files outside the intended theme directory, allowing arbitrary file inclusion.
A system is affected if the Saveo theme version is 1.1.2 or lower AND the theme contains PHP include/require statements that use unsanitized user input, allowing attackers to include arbitrary local files.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of Saveo theme, or if no patch available, implement strict input validation with allowlist filtering on all parameters used in include/require statements, and ensure all include paths are restricted to expected directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-22377 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22377 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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