CVE-2026-22423
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 Select-Themes SetSail setsail allows PHP Local File Inclusion.This issue affects SetSail: from n/a through <= 1.8.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the SetSail theme (Select-Themes) where improper validation of user-controlled input in include/require statements allows attackers to include arbitrary PHP files from the server's filesystem. This can lead to remote code execution if an attacker can upload malicious files or access sensitive configuration 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 SetSail theme installationLocate the theme directory - typically at wp-content/themes/setsail or wp-content/themes/select-themes. Check for the presence of style.css and index.php files with theme identifying headers.Affected if The SetSail/Select-Themes theme directory exists in the WordPress themes folder.
-
Identify the theme versionOpen the theme's style.css file in the theme directory and look for the 'Version:' declaration in the header comments, or check version.php if present.Affected if The installed version is unpatched and matches the vulnerable version range for this LFI flaw.
-
Locate include/require statements using user inputSearch PHP files in the theme directory for patterns like 'include($_GET[' or 'require($_REQUEST[' or 'include($_POST[' without sanitization. Use grep or manual code review to find dynamic include/require calls.Affected if The theme contains include/require statements that directly use unsanitized GET, POST, or REQUEST superglobals.
-
Verify lack of path sanitizationExamine the code around dynamic include/require statements. Check whether basename(), realpath(), or path canonicalization is performed before including files. Look for direct inclusion of user-controlled parameters.Affected if The include/require statements do not use basename(), realpath(), or other path sanitization functions before processing user input.
-
Check for accessible file upload or config directoriesReview whether the web server has write access to directories that could contain malicious PHP files (uploads folder, cache, tmp), or whether sensitive config files (wp-config.php) are readable via the LFI vector.Affected if The server configuration allows uploading files or accessing sensitive configuration files through the vulnerable include mechanism.
You are affected if the SetSail theme is installed with a vulnerable version containing unsanitized user input in include/require statements that can be exploited to include arbitrary local PHP 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 dataImplement strict input validation using basename() and canonicalize paths before include/require statements, or upgrade to a patched version of the SetSail theme if available.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22423 — 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-22423 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