CVE-2026-28086
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 Run Gran run-gran allows PHP Local File Inclusion.This issue affects Run Gran: from n/a through <= 2.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 confidenceLocal File Inclusion (LFI) vulnerability in ThemeREX Run Gran PHP application (version <= 2.0) allows attackers to include arbitrary local files via improper control of filename parameters in include/require statements. This can lead to sensitive file disclosure and potentially 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.
-
Identify if ThemeREX Run Gran PHP application is presentSearch the web root directory for files or directories containing 'themrex' and 'gran' in the path, or look for typical PHP application structures such as index.php, config files, or include/require directories.Affected if The application files are found in the web-accessible directory.
-
Determine the installed version of ThemeREX Run GranOpen version.php, README, or any version file within the application directory. If no version file exists, check the main index.php or config file for version strings or constants.Affected if The discovered version is 2.0 or any version lower than 2.0.
-
Locate include/require statements in the codebaseSearch PHP source files for 'include' and 'require' statements, particularly those using variables or parameters in the file path. Look for patterns like 'include($_GET[...])' or 'require($file)' without proper validation.Affected if The code contains include/require statements that accept user-supplied input without validation.
-
Verify if the vulnerable include/require is accessible via web requestAttempt a test request to suspected endpoints using the include/require functionality with a benign parameter (e.g., ?file=test.php). Check if the application processes the parameter and attempts to include the specified file.Affected if The application processes file parameters in include/require statements through HTTP requests.
You are affected if ThemeREX Run Gran PHP application version 2.0 or lower is installed and the include/require functionality is accessible with user-controlled filename 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 dataImplement strict input validation using whitelist approach for file inclusion paths, sanitize user-supplied input to prevent path traversal sequences (..), and ensure include/require statements only reference intended files within allowed directories.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28086 — 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-28086 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