CVE-2026-22419
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 Honor honor allows PHP Local File Inclusion.This issue affects Honor: from n/a through <= 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 · high confidencePHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Honor theme allows attackers to include arbitrary PHP files from the server due to improper validation of file path parameters used in include/require statements. This can lead to remote code execution if attackers can upload files or access sensitive server files.
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.
-
Locate the Honor theme installationCheck if the theme exists in your WordPress installation under wp-content/themes/honor/ or themes/honor/Affected if The honor theme directory exists on the server
-
Determine the installed versionOpen the theme's style.css file (usually at wp-content/themes/honor/style.css) and check the 'Version:' header in the CSS comment block at the topAffected if The version is 2.3 or lower, or if no version is explicitly declared and the theme file dates are prior to the patch
-
Identify vulnerable file inclusion codeSearch PHP files in the theme (particularly functions.php, header.php, footer.php, and any template files) for include, require, include_once, or require_once statements that use variables or parameters without proper sanitizationAffected if You find include/require statements that incorporate request parameters (like $_GET, $_POST) directly into the file path without validation
-
Test for LFI parameter exposureReview the theme's PHP files to identify which query parameters (in URL or POST data) are passed to include/require functions - check for parameters like 'file', 'page', 'template', 'path', or similar that control file inclusionAffected if The theme accepts and uses user-supplied parameters in file inclusion functions without sanitization using basename() or allowlist validation
Your environment is affected if the AncoraThemes Honor theme version 2.3 or lower is installed AND your server processes PHP files from this theme with user-controlled input reaching include/require statements.
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 filtering on all file inclusion paths, avoid using user-supplied input directly in include/require statements, and consider using a directory-based inclusion approach that restricts file access to expected locations.
- 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-22419 — 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-22419 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