CVE-2026-28021
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 Craftis craftis allows PHP Local File Inclusion.This issue affects Craftis: from n/a through <= 1.2.8.
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 Craftis theme (versions up to 1.2.8) allows attackers to manipulate include/require statements to load arbitrary local PHP files, 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 Craftis theme installationSearch for the theme directory named 'craftis' or 'trx-craftis' in your web application's wp-content/themes/ folder. Common paths: /wp-content/themes/craftis/ or /wp-content/themes/trx-craftis/Affected if The theme directory exists in your WordPress installation
-
Identify installed theme versionOpen the style.css file within the theme directory and locate the 'Version:' header in the CSS comment block at the top of the fileAffected if The version number displayed is 1.2.8 or any lower version (e.g., 1.2.7, 1.2.6, 1.0.0)
-
Find dynamic file inclusion codeSearch PHP files in the theme directory for patterns like 'include($', 'require($', 'include_once($', 'require_once($' combined with $_GET, $_POST, or $_REQUEST variables. Use grep or manually inspect PHP files in the theme folderAffected if You find include/require statements using unsanitized user input from URL parameters
-
Test for LFI parameter exposureExamine URL parameters passed to PHP files within the theme (e.g., ?file=, ?template=, ?path=). Check if these parameters are used in include/require statements without proper validationAffected if Theme files accept file path parameters that can be manipulated to load arbitrary local PHP files
You are affected if ThemeREX Craftis theme version 1.2.8 or lower is installed AND your server serves PHP files from the theme directory with unprotected file inclusion parameters accessible via HTTP requests.
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 whitelist validation, avoid dynamic file inclusion where possible, and ensure PHP open_basedir restrictions are configured.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28021 — 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-28021 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