CVE-2026-28084
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 Bazinga bazinga allows PHP Local File Inclusion.This issue affects Bazinga: from n/a through <= 1.1.9.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the ThemeREX Bazinga theme/plugin (versions up to and including 1.1.9). The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing attackers to manipulate file path parameters to include arbitrary local PHP 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.
-
Identify ThemeREX Bazinga installationSearch your web root for files named 'bazinga' or directories containing 'themerx-bazinga' or 'trx_bazinga'. Check your theme/plugin inventory or composer.json for the ThemeREX Bazinga package.Affected if ThemeREX Bazinga theme or plugin is present in your environment
-
Determine installed versionLocate the main plugin/theme file (typically index.php, main.php, or plugin.php within the bazinga directory) and look for a version constant or header comment displaying the version number.Affected if The version is 1.1.9 or lower
-
Locate include/require statementsSearch the ThemeREX Bazinga source code for PHP include, include_once, require, or require_once statements. Identify which parameters (common names: file, page, template, path, load, action) are used to construct the included file path.Affected if The code contains include/require statements that incorporate user-supplied parameters into file paths
-
Verify parameter accessibilityTest the identified parameters via HTTP requests (GET or POST) to determine if they can be controlled externally. Attempt to include a known local file such as /etc/passwd or a PHPinfo file to confirm LFI is exploitable.Affected if The vulnerable parameters are exposed via URL or form inputs and accept arbitrary file paths without validation
-
Check input validation logicReview the code handling the include/require parameters to see if sanitization or whitelist validation exists. Look for functions like basename(), realpath(), or whitelist arrays that restrict included files.Affected if No input validation exists, or validation can be bypassed, allowing arbitrary file inclusion
Your environment is affected if ThemeREX Bazinga version 1.1.9 or lower is installed and the application exposes parameters used in include/require statements without proper 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 dataRemediate by implementing strict input validation and sanitization on all parameters used in include/require statements, using a whitelist approach for allowed files, and upgrading to a patched version if available.
- 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-28084 — 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-28084 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