CVE-2026-28034
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 Progress progress allows PHP Local File Inclusion.This issue affects Progress: from n/a through <= 1.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 · moderate confidenceThemeREX Progress plugin/theme versions <= 1.2 contains a PHP Local File Inclusion (LFI) vulnerability where improper control of filenames in include/require statements allows attackers to potentially read sensitive files from the server or achieve code execution by manipulating file paths.
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 Progress installationSearch the web server document root for directories or files containing 'themrex' and 'progress' in the name, or check the wp-content/plugins and wp-content/themes directories if this is a WordPress environmentAffected if ThemeREX Progress plugin or theme files are found on the server
-
Identify the installed versionOpen the main plugin/theme PHP file (often named similarly to the directory, e.g., themrex-progress.php) and look for a version definition such as 'Version: x.x' or a $version variable in the header commentsAffected if The version string shows 1.2 or lower, or no version is defined and the product name matches ThemeREX Progress
-
Verify the LFI vulnerable code existsSearch within the ThemeREX Progress directory for PHP include, require, include_once, or require_once statements that use variables in the file path without validation (e.g., include($_GET['file']); or include($path . $_REQUEST['page']);)Affected if File inclusion code uses unvalidated user input (GET, POST, REQUEST parameters) directly in include/require statements
-
Confirm the vulnerable parameter is accessibleIf the vulnerable code uses a specific parameter name (such as 'page', 'file', 'path', or 'template'), attempt a test request to the affected PHP file with that parameter pointing to a non-existent file to see if the application attempts to include itAffected if The server responds to requests with the vulnerable parameter without rejecting the path manipulation
You are affected if ThemeREX Progress is installed with version 1.2 or lower AND the file inclusion code uses unvalidated user-supplied paths that can be manipulated via HTTP parameters.
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 dataUpgrade to a patched version of ThemeREX Progress that implements proper input validation and sanitization on file inclusion paths, ensuring only whitelisted files can be included.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28034 — 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-28034 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