CVE-2026-28018
Local File Inclusion in ThemeREX Global Logistics
Publication date: 2026-03-05
Last updated on: 2026-03-06
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| themerex | globallogistics | to 3.20 (inc) |
| themerex | global_logistics | to 3.20 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-98 | The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-28018 is a Local File Inclusion (LFI) vulnerability in the WordPress Global Logistics Theme versions up to and including 3.20.
This vulnerability allows unauthenticated attackers to include and display local files from the target website by exploiting improper control of filename for include/require statements in PHP.
It is classified under OWASP Top 10 A3: Injection and can be exploited without authentication.
How can this vulnerability impact me? :
Exploitation of this vulnerability could expose sensitive files on the server, such as those containing database credentials.
Depending on the server configuration, this could lead to a complete database takeover.
Because the vulnerability requires no authentication and has a high CVSS score of 8.1, it poses a significant risk to affected websites.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability allows unauthenticated attackers to include and display local files from the target website, which can be detected by monitoring for suspicious HTTP requests attempting to exploit Local File Inclusion (LFI) patterns.
While no specific commands are provided in the available resources, typical detection methods include inspecting web server logs for requests containing suspicious parameters that attempt to include local files, such as those with directory traversal sequences (e.g., ../) or attempts to include sensitive files.
Additionally, applying the mitigation rule released by Patchstack can help block attack attempts, which can also serve as a detection mechanism by logging blocked attempts.
What immediate steps should I take to mitigate this vulnerability?
Since no official patch is currently available for this vulnerability, the immediate recommended step is to implement the mitigation rule released by Patchstack to block attacks targeting this flaw.
Users are strongly advised to apply this mitigation immediately to protect their websites from exploitation.