CVE-2026-27992
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 Meals & Wheels meals-wheels allows PHP Local File Inclusion.This issue affects Meals & Wheels: from n/a through <= 1.1.12.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the ThemeREX Meals & Wheels WordPress plugin (versions up to 1.1.12). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing authenticated attackers to include arbitrary local files from the server, potentially leading to sensitive data disclosure or 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 the Meals & Wheels plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'meals-and-wheels', 'trx_meals', or similar ThemeREX meals-related plugin folder. Alternatively, run 'wp plugin list' if WP-CLI is available.Affected if The plugin folder exists in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin PHP file (usually the first .php file in the plugin folder) and locate the version comment in the file header, or check the plugin's main PHP file for a 'Version:' header comment.Affected if The version is 1.1.12 or lower (any version up to and including 1.1.12)
-
Confirm the vulnerable file inclusion code existsSearch the plugin files for PHP include/require statements that use variable parameters without proper sanitization, such as 'include($_GET[...]' or 'require($_POST[...]'. Focus on files that handle template loading or component rendering.Affected if The plugin contains include/require statements using unsanitized user input from request parameters
-
Verify the vulnerable endpoint is accessibleIdentify PHP files that process file inclusion parameters (commonly named like 'template.php', 'render.php', or files in '/includes/' folders). Attempt a harmless test request to the suspected endpoint using a safe local file path to confirm the parameter accepts arbitrary input.Affected if The endpoint accepts file path parameters without validation and returns file contents
If the Meals & Wheels plugin is installed at version 1.1.12 or below and exposes file inclusion functionality through URL or form parameters, 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 dataDisable or remove the vulnerable Meals & Wheels plugin immediately. Apply any available security patch from ThemeREX. If no patch exists, implement strict input validation on all file inclusion parameters and ensure PHP's allow_url_include is disabled.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27992 — 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-27992 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