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

CVE-2026-28018

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 Global Logistics globallogistics allows PHP Local File Inclusion.This issue affects Global Logistics: from n/a through <= 3.20.

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 PHP Local File Inclusion vulnerability in the ThemeREX Global Logistics theme (versions <= 3.20) allows remote attackers to include arbitrary local files via improperly controlled filename parameters in include/require statements. This can lead to sensitive data exposure (e.g., reading /etc/passwd, configuration files) and potentially remote code execution if attackers can control included PHP files.

MitigationUpgrade to a patched version of the ThemeREX Global Logistics theme. If no patch is available, implement web application firewall rules to block directory traversal patterns (e.g., ../) in URL parameters 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 ThemeREX Global Logistics theme version
    Check the theme's style.css or version.php file typically located in /wp-content/themes/global-logistics/ or /wp-content/themes/trx_gl/ and look for the version comment or $theme_version variable
    Affected if The reported version is 3.20 or lower
  2. Locate vulnerable include/require statements
    Search the theme's PHP files for include(), require(), include_once(), or require_once() calls that use variables (e.g., include($file), require($_GET['filename'])) without proper sanitization, particularly in files under the theme's include/ or inc/ directories
    Affected if Uncontrolled filename parameters are used in include/require statements without validation or sanitization functions such as basename() or realpath()
  3. Identify accessible endpoints
    Review the theme's PHP files (especially in functions.php, template files, or ajax handlers) to identify URL-accessible scripts that accept filename/path parameters via $_GET, $_POST, or $_REQUEST
    Affected if The theme exposes a script that accepts user-controlled path/filename input that gets passed to include/require without validation
  4. Test for directory traversal patterns
    If an endpoint is found, attempt to craft a request with ../../../../etc/passwd or similar path traversal sequences in the filename parameter to see if the application includes arbitrary files
    Affected if The application returns the contents of files outside the theme directory when directory traversal sequences are used in the parameter
  5. Check PHP configuration
    Review the PHP configuration file (php.ini) for the allow_url_include setting; if enabled, this may indicate the system can also include remote files in addition to local files
    Affected if allow_url_include is enabled (though this broadens the attack surface, the CVE specifically targets local file inclusion)

Your environment is affected if the ThemeREX Global Logistics theme version is 3.20 or lower AND your site exposes an endpoint that passes unsanitized filename parameters to PHP include/require statements.

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

Upgrade to a patched version of the ThemeREX Global Logistics theme. If no patch is available, implement web application firewall rules to block directory traversal patterns (e.g., ../) in URL parameters and disable allow_url_include in PHP configuration.

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

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 locally
dbcve dependency scanner

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