CVE-2026-28065
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 Eject eject allows PHP Local File Inclusion.This issue affects Eject: from n/a through <= 2.17.
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 confidenceThe ThemeREX Eject WordPress theme through version 2.17 contains a Local File Inclusion (LFI) vulnerability due to improper control of filenames in PHP include/require statements. This allows attackers to include arbitrary PHP files from the local system, potentially leading to 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.
-
Confirm ThemeREX Eject theme installationNavigate to wp-content/themes/ and verify the eject theme directory exists, or list installed themes via WordPress admin appearance sectionAffected if The ThemeREX Eject theme directory is present in the themes folder
-
Check installed theme versionOpen the theme's style.css file (wp-content/themes/eject/style.css) and locate the 'Version:' header in the theme comment block at the topAffected if The version listed is 2.17 or lower, or if no version is specified but the theme is present
-
Identify file inclusion code pathsSearch the theme's PHP files (particularly in includes/ or any file handling file requests) for patterns like 'include(', 'require(', 'include_once(', 'require_once(' where variables are used directly in the pathAffected if The theme contains PHP files with dynamic file inclusion using unsanitized user-supplied parameters
-
Verify vulnerable parameter exposureReview the theme's PHP files for parameters (commonly 'file', 'path', 'template', 'include', or similar names) passed via GET or POST that are used in inclusion functions without validationAffected if Parameters used in inclusion functions accept user input without whitelist validation or path sanitization
-
Review web server access logsCheck Apache/nginx access logs for requests to the theme directory with suspicious query parameters that may indicate exploitation attempts (e.g., ../../, base64 decode patterns, null byte injection)Affected if Logs show requests targeting the theme with path traversal patterns in query parameters
A user is affected if the ThemeREX Eject theme version is 2.17 or lower AND the theme exposes file inclusion functionality 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 the ThemeREX Eject theme to the latest patched version. If an update is unavailable, disable and replace the theme. Implement input validation on file path parameters and disable allow_url_include in PHP configuration.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28065 — 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-28065 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