CVE-2026-28064
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 Edge Decor edge-decor allows PHP Local File Inclusion.This issue affects Edge Decor: from n/a through <= 2.2.
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 Edge Decor theme (version <= 2.2) contains a Local File Inclusion (LFI) vulnerability where PHP include/require statements improperly validate user-controlled input, allowing attackers to include arbitrary local PHP files and potentially achieve 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.
-
Confirm ThemeREX Edge Decor theme is installedInspect the theme directory (typically wp-content/themes/ folder for WordPress) for the 'trx_edge_decor' or 'edge-decor' theme folder; check style.css for the theme nameAffected if The theme folder exists with this name in the themes directory
-
Check the installed version numberOpen the theme's style.css or functions.php file and locate the 'Version:' header or version definition; compare against <= 2.2Affected if The version listed is 2.2 or lower
-
Identify PHP files using include/require with user inputSearch the theme folder for PHP files containing $_GET, $_POST, or $_REQUEST variables passed directly to include(), require(), include_once(), or require_once() without sanitization (e.g., no basename(), no realpath(), no whitelist check)Affected if Any PHP file in the theme contains user input directly in include/require statements without validation
-
Check for specific file path parametersReview URL-accessible parameters (often named 'file', 'path', 'template', 'page', or 'include') in the theme's PHP files to see if they control which file gets includedAffected if User-controllable parameters directly determine the file path in include/require statements
-
Verify the vulnerable code is reachableConfirm the vulnerable include/require statements are in active code paths (not commented out or behind authentication) by checking for conditional logic that might bypass themAffected if The vulnerable file inclusion code is accessible without authentication or other access controls
If the ThemeREX Edge Decor theme is installed with version 2.2 or lower and contains PHP include/require statements using unsanitized user input, the environment is affected by this LFI vulnerability.
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 and whitelisting for file inclusion paths; avoid using user input directly in include/require statements; use basename() and realpath() to sanitize and validate requested files against an allowed directory.
- 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-28064 — 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-28064 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