CVE-2026-22418
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 Great Lotus great-lotus allows PHP Local File Inclusion.This issue affects Great Lotus: from n/a through <= 1.3.1.
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 the Great Lotus WordPress theme by AncoraThemes allows attackers to include arbitrary PHP files from the server filesystem via improperly controlled filename parameters in include/require statements. This can lead to remote code execution if attackers can control the included 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.
-
Confirm Great Lotus theme installationInspect the WordPress themes directory (wp-content/themes/) for a folder named 'great-lotus' or 'greatlotus', or query the WordPress database wp_options table for the active_theme optionAffected if Great Lotus theme by AncoraThemes is present in the WordPress installation
-
Identify installed theme versionLocate the theme version in the Great Lotus style.css file header (look for 'Version:' field), or in a readme.txt file within the theme folderAffected if Theme version cannot be determined or matches an unpatched release
-
Locate dynamic file inclusion codeSearch PHP files within the Great Lotus theme folder for include(), require(), include_once(), or require_once() statements that use variables or superglobal arrays (e.g., include($file), require($_GET['path'])) without basename() wrapping or whitelist validationAffected if Any include/require statement uses unsanitized user-controlled input as the filename
-
Verify input validation on file inclusionExamine identified include/require statements to confirm whether the filename parameter passes through basename(), pathinfo(), or a whitelist check before useAffected if File inclusion code lacks basename() sanitization or whitelist filtering on the filename parameter
Environment is affected if Great Lotus theme is installed and contains include/require statements that use unsanitized variables or parameters for file paths.
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 dataUpdate to a patched version of Great Lotus if available; otherwise, implement strict input validation using basename() and whitelist approaches on all include/require statements, disable allow_url_include in php.ini, and review code for additional vulnerable file inclusion paths.
- 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-22418 — 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-22418 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