CVE-2026-28028
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 MoneyFlow moneyflow allows PHP Local File Inclusion.This issue affects MoneyFlow: from n/a through <= 1.0.
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 confidenceA Local File Inclusion (LFI) vulnerability exists in the ThemeREX MoneyFlow plugin where user-supplied input is improperly used in PHP include/require statements without sanitization. This allows attackers to include arbitrary local PHP files, potentially leading to sensitive file disclosure or remote code execution depending on server configuration.
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.
-
Identify ThemeREX MoneyFlow plugin installationLocate the ThemeREX MoneyFlow plugin directory in the web root, typically under wp-content/plugins/ or similar CMS plugin paths. List installed plugins to confirm presence.Affected if The plugin is present in the environment regardless of version.
-
Determine installed plugin versionCheck the main plugin PHP file for a version constant or header comment, or inspect the plugin's metadata file (plugin.json, readme.txt) for version information.Affected if Any installed version of ThemeREX MoneyFlow plugin is present since no safe version range was specified.
-
Inspect for dynamic include/require patternsSearch all PHP files within the plugin directory for include(), require(), include_once(), or require_once() statements where variables or user-supplied parameters are used directly in the path argument without sanitization or whitelist validation.Affected if Dynamic include/require statements using unsanitized input (such as $_GET, $_POST, or other user-controllable variables) are found in the plugin code.
-
Verify the vulnerable parameter is accessibleIdentify which URL parameters or input vectors feed into the include/require statements. Test whether these parameters can be controlled via HTTP requests to the affected application endpoint.Affected if User-controllable input can reach the include/require logic without validation.
-
Check PHP allow_url_include settingInspect php.ini or run phpinfo() to determine if the allow_url_include directive is enabled. This configuration can elevate LFI to remote code execution if the application permits including remote URLs.Affected if allow_url_include is enabled (value is On).
A defender is affected if ThemeREX MoneyFlow plugin is installed and its code contains dynamic include/require statements using unsanitized user input, regardless of the specific version.
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 dataReplace dynamic include/require statements with a whitelist approach or validate all input against a strict allowlist of permitted files. Disable allow_url_include if not needed, and ensure web server runs with minimal file system permissions.
- 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-28028 — 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-28028 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