CVE-2026-28096
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 WealthCo wealthco allows PHP Local File Inclusion.This issue affects WealthCo: from n/a through <= 2.18.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability in ThemeREX WealthCo theme (versions up to 2.18) allows attackers to include arbitrary PHP files from the server through improper input validation on file inclusion functions (include/require). This can lead to remote code execution if attackers can control the included file path.
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 ThemeREX WealthCo theme and identify versionCheck the theme directory (typically /wp-content/themes/wealthco/ or similar) and open style.css to find the 'Version:' header in the theme comment blockAffected if Theme version is 2.18 or lower, or if version line is missing/unreadable but theme name matches WealthCo
-
Compare installed version to affected rangeIf version is readable, compare it numerically to 2.18. Any version up to and including 2.18 is within the affected rangeAffected if Installed version is 2.18 or any lower version number
-
Identify file inclusion code in theme PHP filesSearch theme PHP files (especially in functions.php, header.php, or template files) for include, require, include_once, or require_once statements that use variables without sanitization (e.g., include($_GET['template'], include($file))Affected if Unsanitized user input is used directly in include/require functions
-
Locate the vulnerable parameterExamine the include/require statements found in step 3 to identify which URL parameter (e.g., $_GET['file'], $_GET['template']) controls the included file pathAffected if A GET parameter is used in file inclusion without input validation or whitelist filtering
-
Test parameter accessibilityAttempt to include a benign local file (e.g., ../index.php) via the identified parameter to confirm the vulnerability is exploitableAffected if The parameter successfully includes arbitrary local files, confirming LFI is present
You are affected if the WealthCo theme is installed at version 2.18 or lower AND your server exposes a file inclusion parameter that accepts unsanitized user input.
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 WealthCo theme to the latest patched version. If no patch is available, implement strict input validation on all file inclusion parameters and disable allow_url_include. Restrict file inclusion to whitelist-based approaches.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28096 — 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-28096 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