CVE-2026-22477
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 Felizia felizia allows PHP Local File Inclusion.This issue affects Felizia: from n/a through <= 1.3.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 confidenceA PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Felizia theme (versions up to 1.3.4) allows attackers to manipulate file inclusion paths to execute arbitrary PHP code on the server. This stems from improper input validation on include/require statements.
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 if Felizia theme is installedCheck your web server's themes or wp-content/themes directory for a folder named 'felizia' or similar. For WordPress, list all installed themes via admin panel or filesystem.Affected if The Felizia theme by AncoraThemes is present in the web application's theme directory.
-
Determine theme versionCheck theme's style.css or functions.php file for a 'Version:' header, or look for a version.php file within the theme directory.Affected if The installed version is unknown, unpatched, or falls within any vulnerable version range for this theme.
-
Identify exposed file inclusion parametersSearch web server logs, fuzz URL parameters, or review theme source code (particularly PHP files with include/require statements) for parameters that accept filename or path input.Affected if A parameter accepting user input (e.g., ?file=, ?template=, ?page=, ?filename=) is used in include/require statements without sanitization.
-
Test for path traversal vulnerabilityAttempt a controlled LFI probe using a safe test (e.g., requesting a parameter with ../../../../etc/passwd or ../../../../windows/system32/drivers/etc/hosts) if you have authorization to test your own environment.Affected if The application returns file contents from outside the intended directory, confirming path traversal is possible.
You are affected if the Felizia theme is installed and exposes any URL parameter used in PHP include/require statements without basename() or realpath() sanitization, allowing path traversal to read 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 if available; otherwise, implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22477 — 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-22477 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