CVE-2026-28017
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 Green Thumb greenthumb allows PHP Local File Inclusion.This issue affects Green Thumb: 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 confidenceA Local File Inclusion (LFI) vulnerability in the ThemeREX Green Thumb greenthumb component allows attackers to control the filename parameter in PHP include/require statements, enabling arbitrary file reads from the server filesystem. This affects all versions up to and including 1.1.12.
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 greenthumb component in your environmentSearch your web root directories for files or directories named 'greenthumb' or 'green-thumb', or check your CMS/theme plugin list if using a content management system that integrates the ThemeREX greenthumb component.Affected if The greenthumb component is present in your environment.
-
Identify the installed greenthumb versionOpen the main greenthumb component file (often named greenthumb.php or within a greenthumb folder) and locate the version declaration in the header comments, plugin metadata, or a dedicated version/configuration file.Affected if The version is 1.1.12 or lower.
-
Verify the vulnerable file inclusion functionality is accessibleExamine the greenthumb PHP files for include, require, include_once, or require_once statements that accept a variable or parameter for the file path (look for patterns like include($file), require($_GET['file']), etc.).Affected if The component contains file inclusion logic that uses unsanitized user input for the filename parameter.
-
Test if the LFI parameter is exposed via web requestIf identified, attempt a benign local file read request (such as including a known static file like a configuration file using the suspected parameter) through the greenthumb component's web-accessible endpoint.Affected if The component accepts and processes file path parameters without validation, allowing local file inclusion.
You are affected if the greenthumb component is installed, its version is 1.1.12 or lower, and the file inclusion functionality with the vulnerable filename parameter is accessible.
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 the greenthumb component; as an immediate defense-in-depth measure, disable allow_url_include in php.ini and implement strict input validation on any file path parameters.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28017 — 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-28017 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