CVE-2026-28012
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 Gridiron gridiron allows PHP Local File Inclusion.This issue affects Gridiron: from n/a through <= 1.0.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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability in ThemeREX Gridiron (versions through 1.0.14) allows attackers to include arbitrary local PHP files due to improper control of filename parameters in include/require statements. This can lead to code execution if attackers can control the included files.
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 Gridiron installationSearch for theme files named 'gridiron' or 'trx_gridiron' in your web root directories, typically under wp-content/themes/ or wp-content/plugins/Affected if ThemeREX Gridiron files are found in the environment
-
Identify the installed versionOpen the main plugin/theme file (usually index.php, style.css, or plugin header) and look for a version comment or constant such as 'Version: x.x.x'Affected if The version is 1.0.14 or lower, or no version is displayed (implying an old unpatched release)
-
Search for vulnerable include/require patternsGrep the codebase for patterns like 'include($_GET[' or 'require($_POST[' or 'include($_REQUEST[' followed by a file path, looking specifically in files under the gridiron directoryAffected if Code directly uses unsanitized request parameters (GET, POST, REQUEST) in include or require statements without validation
-
Identify the vulnerable parameter nameExamine the include/require statements found and note the parameter name used (commonly 'file', 'page', 'include', 'path', or similar)Affected if A parameter accepting file paths is used directly in include/require without sanitization
-
Verify parameter accessibilityTest if the identified parameter can be controlled via URL query string or POST data (e.g., append '?param=../../wp-config.php' to a page using the gridiron component)Affected if The parameter accepts arbitrary file paths and the application does not reject or sanitize path traversal attempts
You are affected if ThemeREX Gridiron version 1.0.14 or lower is installed and the codebase contains direct use of request parameters in include/require statements without input validation.
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 on all include/require parameters using allowlists, validate that the requested path stays within expected directories, and update to a patched version if available.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28012 — 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-28012 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