CVE-2026-22380
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 UnlimHost unlimhost allows PHP Local File Inclusion.This issue affects UnlimHost: from n/a through <= 1.2.3.
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 (LFI) vulnerability in AncoraThemes UnlimHost allows attackers to manipulate file inclusion functions (include/require) to access arbitrary files on the server by providing crafted file paths. This can lead to exposure of sensitive configuration files, source code, credentials, and potentially remote code execution.
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.
-
Confirm UnlimHost product installationIdentify if the web application running is AncoraThemes UnlimHost by checking site metadata, theme headers, or vendor documentationAffected if The application is AncoraThemes UnlimHost
-
Determine installed versionLocate the version file or header for UnlimHost (commonly in theme style.css, package.json, or a version.php/config file within the theme or plugin directory)Affected if Version cannot be determined or differs from the latest patched release
-
Identify file inclusion code patternsSearch source code for include, require, include_once, or require_once statements that concatenate user input (e.g., $_GET, $_POST, or request parameters) directly into file paths without validationAffected if Unsanitized user-supplied values are passed to inclusion functions
-
Inspect URL parameters used in inclusion logicTest common file inclusion parameters (such as 'page', 'file', 'path', 'template', 'load', or 'include' in URLs) by providing benign file paths like '/etc/passwd' or '../../config.php' to observe if content is returnedAffected if Application returns contents of files outside the intended directory
-
Review base path configurationCheck that all include/require statements use a fixed base directory (e.g., defined constants or variables) and do not rely on user input to determine the directory portion of the file pathAffected if File inclusion logic lacks a fixed base path or allows directory traversal
You are affected if UnlimHost is installed, file inclusion functions use unsanitized user input, and the application returns arbitrary file contents when traversal sequences are provided in URL parameters.
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 dataImplement strict input validation using whitelist-based allowlists for permitted files, use basename() to extract only the filename component, disable allow_url_fopen and allow_url_include, and ensure all include/require statements use fixed base paths.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22380 — 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-22380 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