CVE-2026-57801
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 <= 2.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 · high confidenceLocal File Inclusion (LFI) vulnerability in the SetSail WordPress theme by Select-Themes allows attackers to include arbitrary local PHP files via improper input validation in include/require statements, potentially leading to remote code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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.
-
Verify SetSail theme is installedCheck your WordPress installation's wp-content/themes/ directory for a folder named 'setsail' or 'Select-Themes' or 'setsail'Affected if The SetSail theme folder exists in your WordPress themes directory
-
Identify the installed theme versionOpen the style.css file within the SetSail theme folder and locate the 'Version:' header in the file commentsAffected if The version number you find is older than the latest patched version from Select-Themes
-
Search for vulnerable include/require patternsInspect PHP files in the theme folder for include, include_once, require, or require_once statements that use variables without sanitization (e.g., include($var), require($_GET['page']))Affected if Any theme PHP files contain include/require statements that incorporate unsanitized user input from GET, POST, or COOKIE parameters
-
Test for path traversal capabilityIf vulnerable include patterns exist, verify if the web server has read access to sensitive local files outside the theme directory (check file permissions on wp-config.php and system files)Affected if The web server process can read files outside the web root via the vulnerable inclusion point
-
Check WordPress admin accessReview whether untrusted users can upload or modify theme files via the WordPress admin panelAffected if Users with limited or no admin privileges can upload or modify PHP files in the theme
Your environment is affected if the SetSail theme by Select-Themes is installed and contains include/require statements that accept unsanitized user input, allowing path traversal to 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 dataUpdate SetSail theme to the latest patched version; if no update available, implement strict input validation and whitelist-based file inclusion controls to prevent path traversal.
- Consultation4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57801 — 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-57801 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