CVE-2026-28087
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 Filmax filmax allows PHP Local File Inclusion.This issue affects Filmax: from n/a through <= 1.1.11.
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 vulnerability in ThemeREX Filmax theme allows attackers to manipulate filename parameters in include/require statements, potentially reading sensitive files from the server filesystem. This stems from improper input validation on file path parameters.
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 Filmax theme is installedCheck the wp-content/themes directory for the filmax theme folder. In WordPress admin, navigate to Appearance > Themes to confirm the active or installed theme.Affected if The ThemeREX Filmax theme is present in the WordPress installation
-
Locate file inclusion code in theme PHP filesSearch the theme directory for PHP files containing include, include_once, require, or require_once statements that use variables without proper sanitization. Use grep or similar: grep -r 'include\|require' --include='*.php' in the theme folder.Affected if Files contain include/require statements using raw user input without validation
-
Identify the vulnerable parameterExamine the include/require statements found to identify which $_GET, $_POST, or $_REQUEST parameters are used in the file path. Look for patterns like include($_GET['param']) or require($var) without basename() or realpath() validation.Affected if A parameter controllable via URL or request is used directly in include/require without sanitization
-
Verify path traversal is possibleTest if the vulnerable parameter accepts paths like ../../../../etc/passwd or ../wp-config.php. Attempt to access a known local file through the parameter to confirm the LFI exists.Affected if The parameter allows path traversal sequences and returns file contents outside the theme directory
-
Check if the vulnerable endpoint is accessibleDetermine if the file containing the vulnerable code can be accessed without authentication. Check if the code executes in the context of a publicly accessible WordPress page or AJAX handler.Affected if The vulnerable code can be triggered by an unauthenticated attacker
If the ThemeREX Filmax theme is installed and contains PHP files with unauthenticated include/require statements using unsanitized user input for file paths, the environment is affected by this LFI vulnerability.
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 the Filmax theme to the latest patched version available from ThemeREX. If no patch exists, audit and harden include/require statements to enforce strict allowlist validation on file path parameters.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28087 — 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-28087 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