CVE-2026-28061
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 Tiger Claw tiger-claw allows PHP Local File Inclusion.This issue affects Tiger Claw: from n/a through <= 1.1.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 file inclusion vulnerability in ThemeREX Tiger Claw (version <= 1.1.14) allows attackers to include arbitrary files through unsanitized input in include/require statements, potentially leading to 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.
-
Locate ThemeREX Tiger Claw installationSearch the web root for directories or files containing 'tiger' or 'themerex' in the name. Common paths include /wp-content/plugins/ or /wp-content/themes/. Use: find /path/to/webroot -iname '*tiger*' -o -iname '*themerex*'Affected if The plugin or theme files are found on the system
-
Identify installed versionCheck the main plugin/theme PHP file for a version constant or header comment. Common locations: plugin main file header, style.css (for themes), or a dedicated version.php file. Look for 'Version: X.X.X' or '$version = 'Affected if The version is 1.1.14 or lower
-
Identify vulnerable file inclusion pointsSearch PHP files in the plugin/theme for include/require statements using variables: grep -rn 'include\|require' --include='*.php' | grep -E '\$_GET|\$_REQUEST' to find file inclusion code that uses user inputAffected if File inclusion code using unvalidated $_GET or $_REQUEST parameters is found
-
Test for LFI parameter exposureExamine URL parameters used in include/require statements. Typical vulnerable patterns include ?file= or ?template= or ?path= pointing to include statements. Review the code flow from request to include statementAffected if A parameter controllable via GET/POST is used directly in include/require without sanitization
-
Verify parameter is accessibleAttempt a benign include test using a known readable file (e.g., /etc/passwd or a local PHP file) via the identified parameter. Observe if the file contents are returned or if PHP parsing occursAffected if The application returns contents of arbitrary local files or executes PHP from files specified via the parameter
The environment is affected if ThemeREX Tiger Claw version 1.1.14 or lower is installed and contains file inclusion code that uses unvalidated user-supplied input in include/require statements.
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 parameters used in include/require statements, disable allow_url_include in PHP configuration, and update to a patched version if available.
- Consultation4.0 h
- Implementation6.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 $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28061 — 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-28061 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