CVE-2026-22478
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 Elated-Themes FindAll findall allows PHP Local File Inclusion.This issue affects FindAll: from n/a through <= 1.4.
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 confidencePHP Local File Inclusion (LFI) vulnerability in Elated-Themes FindAll allows attackers to include arbitrary local files via unsanitized user input in include/require statements. This can enable reading sensitive files on the server such as configuration files, credentials, or source code.
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 the applicationSearch your web root for files containing 'FindAll' or 'elated-themes' in their content or check CMS/theme documentation to confirm Elated-Themes FindAll is installedAffected if Elated-Themes FindAll is present in the environment
-
Locate PHP include/require statementsSearch PHP files in the theme/application for patterns like 'include($', 'require($', 'include_once($', or 'require_once($' that accept user-supplied parametersAffected if Dynamic include or require statements using variable input are found in the codebase
-
Check for unsanitized user input in includesExamine the identified include/require statements to see if user input (e.g., $_GET, $_POST, $_REQUEST) is passed directly without validation, sanitization, or whitelist filteringAffected if User-controlled input flows directly into include/require without validation or allowlisting
-
Determine if the vulnerable parameter is accessibleTest accessing the suspected parameter via URL (e.g., ?page=../../../etc/passwd) or HTTP request to confirm it is not protected by authentication or other access controlsAffected if The parameter accepting user input is reachable without authentication and accepts path traversal sequences
-
Verify file read capabilityAttempt to include a known safe local file (e.g., a configuration file in the web root) through the suspected parameter to confirm the LFI behaviorAffected if The application successfully includes and outputs content from local files based on user-supplied paths
If Elated-Themes FindAll is installed and user input flows unsanitized into dynamic include/require statements that are accessible, the environment is affected by CVE-2026-22478.
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 with whitelist-based allowlisting for included files, or refactor to use a switch/case pattern instead of dynamic includes. Upgrade to a patched version if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22478 — 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-22478 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