CVE-2026-28023
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 Nuts nuts allows PHP Local File Inclusion.This issue affects Nuts: from n/a through <= 1.10.
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 confidenceA PHP Local File Inclusion vulnerability in the ThemeREX Nuts theme allows attackers to include arbitrary PHP files from the server through improper control of filenames 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.
-
Locate ThemeREX Nuts CMS theme installationSearch the web server document root for directories named 'trx_nuts', 'nuts', or 'themrex' typically under /wp-content/themes/ (WordPress) or /themes/ (standalone). Also check for files containing 'ThemeREX' or 'Nuts' in the name.Affected if ThemeREX Nuts CMS theme files are present on the server
-
Identify PHP files with include/require statementsGrep all .php files in the theme directory for patterns like 'include(', 'require(', 'include_once(', 'require_once(' followed by variables such as $_GET, $_POST, or $_REQUEST.Affected if The theme contains PHP files that dynamically include files based on user input
-
Examine variable handling in include/require statementsReview the identified PHP files to see if the variables used in include/require statements receive input directly from $_GET, $_POST, or $_REQUEST parameters without sanitization functions like basename() or realpath().Affected if User-supplied parameters flow into include/require without validation or path sanitization
-
Check for path traversal protectionSearch the include/require code for security measures: basename(), realpath(), preg_replace with traversal pattern removal, or whitelist validation. Verify if these checks occur BEFORE the include/require call.Affected if No path traversal protection exists or protection can be bypassed before file inclusion occurs
-
Verify web server access to sensitive filesConfirm the web server user (www-data, apache, nginx) has read permissions on sensitive files like /etc/passwd or application configuration files that could be targeted.Affected if The web server process can read sensitive local files accessible via path traversal
If ThemeREX Nuts CMS theme is installed AND contains PHP files using user input in include/require statements without proper path traversal validation, the environment is vulnerable to CVE-2026-28023.
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 dataRestrict file inclusion paths using whitelist validation, basename(), or directory locking, and ensure user-supplied input is never used directly in include/require statements.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28023 — 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-28023 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