CVE-2026-28022
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 Foodie foodie allows PHP Local File Inclusion.This issue affects Foodie: from n/a through <= 1.14.
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 confidenceLocal File Inclusion (LFI) vulnerability in ThemeREX Foodie plugin/theme (versions up to 1.14) allows attackers to include arbitrary local files via improper validation of file paths in PHP include/require statements. This can lead to exposure of sensitive files such as configuration files, credentials, or source code.
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 Foodie installationSearch your web server file system for directories or files containing 'trx_foodie', 'themerex_foodie', or 'foodie' in the plugins (/wp-content/plugins/) or themes (/wp-content/themes/) directoriesAffected if ThemeREX Foodie plugin or theme files are found on the server
-
Identify installed versionOpen the main plugin/theme PHP file (often named index.php, init.php, or the main plugin file) and locate the version declaration (commonly 'Version:' in file headers, or a $version variable). Compare this version number to the affected range (1.14 and below)Affected if The installed version is 1.14 or lower
-
Examine file inclusion codeSearch all PHP files in the ThemeREX Foodie directory for include, include_once, require, or require_once statements that accept variables in the path (e.g., include($file), include($_GET['path'])) without proper validationAffected if PHP files contain include/require statements using unsanitized variable paths
-
Verify directory traversal vulnerabilityReview the identified include/require code paths to confirm they do not use basename() or whitelist validation, and that parameters like 'file', 'path', 'page', or 'template' can be manipulated with ../ sequencesAffected if File inclusion code allows directory traversal (../) without validation using basename() or whitelist checks
-
Check web server access to sensitive filesConfirm that the web server user has read access to sensitive system files such as /etc/passwd, configuration files in /wp-config.php, or other application config files that could be exposed via the LFIAffected if The web server process can read sensitive files that could be included via the LFI vulnerability
If ThemeREX Foodie version 1.14 or lower is installed AND contains PHP include/require statements using unsanitized variable paths that allow directory traversal, the environment is affected by this CVE.
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 whitelist-based input validation for file paths in include/require statements, use basename() to strip directory traversal sequences, and ensure all file inclusion operations validate against an allowed directory.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28022 — 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-28022 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