PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-28091

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX Coleo coleo allows PHP Local File Inclusion.This issue affects Coleo: from n/a through <= 1.1.7.

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 confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the ThemeREX Coleo theme (versions up to 1.1.7). The vulnerability stems from improper control of filename parameters in PHP include/require statements, allowing attackers to manipulate file paths to include arbitrary local PHP files, potentially leading to remote code execution.

MitigationUpdate to the latest patched version of the ThemeREX Coleo theme. If no patch is available, audit and harden all include/require statements to use whitelist validation and disable allow_url_include in PHP configuration.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ThemeREX Coleo theme is present
    Locate PHP theme files named 'Coleo' or 'coelo' in your web server's theme directory (commonly wp-content/themes/). Check for a style.css file containing 'Theme Name: Coleo' or 'ThemeREX' branding.
    Affected if The Coleo theme files exist in the environment
  2. Determine the installed Coleo theme version
    Open the theme's style.css file (wp-content/themes/[coelo-folder]/style.css) and locate the 'Version:' header in the CSS comment block at the top. Compare this version number against any known affected version ranges for this CVE.
    Affected if The installed version falls within the affected version range for this vulnerability
  3. Search for vulnerable include/require patterns
    Grep or search through all PHP files in the theme directory for patterns like 'include($_', 'require($_', 'include_once($_', 'require_once($_' where the variable is not validated with allowlist checks before use.
    Affected if PHP files contain include/require statements using raw user input variables without validation
  4. Inspect the vulnerable code for filename parameter usage
    Examine the identified include/require statements in detail. Check if the variable used (e.g., $_GET['filename'], $_POST['file']) is passed directly to include/require without sanitization, allowlisting, or path traversal checks.
    Affected if The filename parameter is used directly in include/require without input validation or allowlist checks
  5. Verify web accessibility of vulnerable paths
    Determine if the PHP files containing the vulnerable code are accessible via HTTP/HTTPS requests to the web server. Test if the vulnerable parameter can be manipulated through URL parameters.
    Affected if The vulnerable PHP files are web-accessible and the parameter can be supplied via HTTP requests

You are affected if the Coleo theme is installed, contains include/require statements using unvalidated user-supplied filename parameters, and those scripts are accessible via the web server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of the ThemeREX Coleo theme. If no patch is available, audit and harden all include/require statements to use whitelist validation and disable allow_url_include in PHP configuration.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28091 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28091 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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