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

CVE-2026-28097

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 Artrium artrium allows PHP Local File Inclusion.This issue affects Artrium: from n/a through <= 1.0.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 confidence

A Local File Inclusion (LFI) vulnerability in the ThemeREX Artrium WordPress theme allows attackers to include arbitrary local PHP files via improperly controlled input in include/require statements. This can lead to code execution, sensitive file disclosure, or further compromise of the WordPress installation.

MitigationImplement strict input validation using an allowlist approach on any parameters used in include/require statements, or refactor code to avoid user-controlled file paths entirely. Ensure all file inclusion functions use sanitized, hardcoded paths rather than dynamic user input.

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 Artrium theme is installed
    Navigate to Appearance > Themes in WordPress admin panel, or inspect /wp-content/themes/ directory for the artrium theme folder
    Affected if The ThemeREX Artrium theme is present in the WordPress installation
  2. Identify the theme version
    Check the theme's style.css file (usually in /wp-content/themes/artrium/) for the 'Version:' header in the stylesheet comments, or check theme functions.php for a version constant
    Affected if Version is at or below the vulnerable release (confirm via Themeforest or theme changelog if version data is available)
  3. Locate vulnerable include/require patterns
    Search theme PHP files for dynamic include/require statements that use $_GET, $_POST, or $_REQUEST parameters directly without sanitization. Focus on files in the theme's include/ or inc/ directories
    Affected if Code contains patterns like include($_GET['parameter']) or require($_REQUEST['file']) without validation
  4. Identify the vulnerable parameter
    Review the dynamic file inclusion code found in step 3 to identify which URL parameter controls the file path (common names: file, page, template, include, path, theme, lang)
    Affected if A URL parameter is used in include/require without allowlist validation or basename() filtering
  5. Test if the parameter is externally accessible
    Attempt a benign LFI test: access a page with the vulnerable parameter appended (e.g., ?file=../../../../wp-config.php) and observe if file contents are returned or if PHP error messages reveal the path
    Affected if The parameter is accepted by the application and returns file contents or path information
  6. Check server configuration
    Inspect wp-config.php and server configuration (httpd.conf, .htaccess) for PHP settings that may limit LFI exploitation such as open_basedir restrictions or disable_functions
    Affected if PHP is configured to allow file inclusion from arbitrary paths (open_basedir not restricting the theme directory)

A user is affected if the ThemeREX Artrium theme is installed with a vulnerable version AND the application accepts unsanitized input in file inclusion parameters that can be manipulated to read arbitrary local files.

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

Implement strict input validation using an allowlist approach on any parameters used in include/require statements, or refactor code to avoid user-controlled file paths entirely. Ensure all file inclusion functions use sanitized, hardcoded paths rather than dynamic user input.

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-28097 — 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-28097 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