CVE-2026-28051
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 ThemeREX Yacht Rental yacht-rental allows PHP Local File Inclusion.This issue affects Yacht Rental: from n/a through <= 2.6.
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 vulnerability in ThemeREX Yacht Rental theme versions <= 2.6 allows attackers to include arbitrary local PHP files via improper control of filename parameters 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
- 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 ThemeREX Yacht Rental theme is installedCheck your WordPress installation's wp-content/themes/ directory for a folder named 'yacht-rental' or similar ThemeREX yacht theme folder. Also check via WordPress admin under Appearance > Themes.Affected if The theme folder exists in your WordPress themes directory.
-
Determine the installed theme versionOpen the theme's style.css file in the theme folder and look for the 'Version:' header in the comment block at the top. Alternatively, check version.php if present in the theme root directory.Affected if The version listed is 2.6 or lower.
-
Search for vulnerable include/require patterns in theme filesUse grep or a file search to look for include(), require(), include_once(), or require_once() statements that use $_GET, $_POST, or $_REQUEST variables directly in the filename parameter, for example: include($_GET['file']). Check PHP files in the theme folder, particularly in any 'include' or 'components' subdirectories.Affected if You find include/require statements that use unsanitized user input from $_GET, $_POST, or $_REQUEST as the file path.
-
Check PHP configuration for allow_url_includeCreate a PHP file with phpinfo(); access it via browser, or run 'php -i' from command line, and look for the allow_url_include setting in the PHP Core section.Affected if allow_url_include is set to On (this enables remote file inclusion in addition to local file inclusion, increasing exploit severity).
Your environment is affected if the ThemeREX Yacht Rental theme version is 2.6 or lower AND you have include/require statements using unsanitized request parameters in your theme 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 the yacht-rental theme to the latest patched version. If no patch available, implement strict input validation and whitelisting on any parameters used in include/require statements, and ensure allow_url_include is disabled in PHP configuration.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28051 — 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-28051 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