CVE-2026-28094
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 RexCoin rexcoin allows PHP Local File Inclusion.This issue affects RexCoin: from n/a through <= 1.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 confidenceA PHP Local File Inclusion (LFI) vulnerability in ThemeREX RexCoin allows attackers to manipulate include/require statements by controlling the filename parameter, potentially executing arbitrary PHP code or reading sensitive files from the server.
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 RexCoin theme is installedCheck your WordPress installation themes directory for the RexCoin theme folder, typically found in wp-content/themes/ and confirm the theme name and version in style.css or theme.jsonAffected if ThemeREX RexCoin theme is present in the WordPress themes directory
-
Locate PHP files that perform file inclusionSearch the RexCoin theme directory for PHP files containing include, include_once, require, or require_once statements, particularly those using variables as the file pathAffected if File inclusion functions are used within the theme PHP files
-
Identify the vulnerable filename parameterExamine include/require statements to determine if a filename or path parameter can be influenced by user-supplied input such as GET, POST, or REQUEST superglobalsAffected if User-controlled input from GET/POST/REQUEST parameters flows directly into include/require statements without validation
-
Verify lack of input validation on file inclusion parametersReview the code around vulnerable include/require calls to check whether the filename parameter undergoes strict allowlist validation, path sanitization, or directory containment before useAffected if The filename parameter accepts arbitrary file paths without validation or sanitization against an allowlist of permitted files/directories
-
Check file permissions and directory accessReview whether the web server process has read access to sensitive system files or directories outside the expected theme/includes foldersAffected if The PHP process can read files outside the intended theme directory through the LFI vulnerability
A user is affected if the ThemeREX RexCoin theme is installed and contains file inclusion code where user-supplied input is used in include/require statements without validation, allowing path manipulation.
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 on file inclusion parameters using allowlists, avoid user-supplied input in include/require statements, and ensure all file paths are sanitized and constrained to expected directories.
- 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-28094 — 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-28094 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