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

CVE-2026-28019

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 Manoir manoir allows PHP Local File Inclusion.This issue affects Manoir: from n/a through <= 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 · high confidence

The ThemeREX Manoir WordPress theme <= 1.11 contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filenames used in include/require statements. Attackers can manipulate input parameters to include arbitrary PHP files from the server, potentially leading to remote code execution.

MitigationUpdate the ThemeREX Manoir theme to the latest patched version. If no update is available, disable the theme immediately and replace with a secured alternative, or manually audit and fix the file inclusion logic to properly validate and sanitize all include/require path inputs.

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. Confirm ThemeREX Manoir theme is installed
    Locate the theme directory on the web server. Common paths include wp-content/themes/themerex-manoir for WordPress installations or the themes folder in the application root. Check for a style.css or theme.json file containing 'ThemeREX Manoir' as the theme name.
    Affected if The theme directory exists and contains ThemeREX Manoir theme files.
  2. Determine installed theme version
    Open the theme's style.css file (typically in the theme root) and locate the 'Version:' comment in the file header. Alternatively, check theme.json for a version field. Compare this version number against any official changelogs or release notes from ThemeREX.
    Affected if The installed version is older than the patched version released for this CVE.
  3. Identify PHP files with include/require usage
    Search the theme directory for PHP files containing include, require, include_once, or require_once statements. Use grep or a file search tool: grep -r "include(" or grep -r "require(" within the theme folder. Review each file to see if the included path uses a variable rather than a hardcoded string.
    Affected if PHP files in the theme contain dynamic include/require statements that accept variables as filenames.
  4. Check for user input reaching include/require
    Examine the PHP files identified in the previous step. Trace the variables used in include/require statements back to their source. Look for $_GET, $_POST, $_REQUEST, or other superglobal variables being passed directly or indirectly to these statements. Check if the input undergoes any validation before being used.
    Affected if User-supplied parameters (from URL, form, or cookies) are used in include/require statements without proper sanitization.
  5. Test for vulnerable parameter patterns
    If the theme is running, attempt a controlled test using a benign local file path in the suspected parameter (such as ../../../../etc/passwd or the theme's own PHP files). Monitor whether the application includes the file content. Only perform this on non-production systems or with explicit authorization.
    Affected if The application reflects the contents of arbitrary local files when supplied via URL parameters used in include/require logic.

You are affected if the ThemeREX Manoir theme is installed and user-controlled input reaches include/require statements without validation, allowing arbitrary file inclusion.

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 the ThemeREX Manoir theme to the latest patched version. If no update is available, disable the theme immediately and replace with a secured alternative, or manually audit and fix the file inclusion logic to properly validate and sanitize all include/require path inputs.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-28019 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