CVE-2026-28097
Received Received - Intake
Local File Inclusion in ThemeREX Artrium ≀1.0.14 Allows Code Execution

Publication date: 2026-03-05

Last updated on: 2026-03-05

Assigner: Patchstack

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-05
Last Modified
2026-03-05
Generated
2026-05-27
AI Q&A
2026-03-05
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
themerex artrium From 1.0.0 (inc) to 1.0.14 (inc)
themerex artrium to 1.0.14 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


Can you explain this vulnerability to me?

CVE-2026-28097 is a Local File Inclusion (LFI) vulnerability found in the WordPress Artrium Theme versions up to and including 1.0.14. It arises from improper control of filenames used in include or require statements in PHP, allowing an attacker to include and display local files from the target website.

This means an unauthenticated attacker can exploit this flaw to access sensitive files on the server, potentially exposing critical information.


How can this vulnerability impact me? :

[{'type': 'paragraph', 'content': 'Exploitation of this vulnerability can lead to the exposure of sensitive information such as database credentials by including local files from the server.'}, {'type': 'paragraph', 'content': "Depending on the website's configuration, an attacker could leverage this information to perform a complete database takeover."}, {'type': 'paragraph', 'content': 'The vulnerability is considered high risk with a CVSS score of 8.1, indicating a high likelihood of exploitation and severe impact.'}] [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability allows an attacker to include and display local files via the WordPress Artrium Theme, which can be detected by monitoring for suspicious HTTP requests attempting to exploit Local File Inclusion (LFI).'}, {'type': 'paragraph', 'content': 'Detection can involve inspecting web server logs for requests containing suspicious parameters or payloads that try to include local files, such as those containing directory traversal sequences (e.g., ../) or attempts to include sensitive files like /etc/passwd.'}, {'type': 'paragraph', 'content': 'Example commands to detect such attempts include using grep on web server logs:'}, {'type': 'list_item', 'content': "grep -i 'include' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "grep -E '\\.\\./|etc/passwd|boot.ini' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "tail -f /var/log/apache2/access.log | grep -i 'artrium'"}, {'type': 'paragraph', 'content': 'Additionally, network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to detect and alert on patterns consistent with LFI attacks targeting this theme.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include applying the Patchstack mitigation rule designed to block attacks targeting this Local File Inclusion vulnerability in the Artrium theme.

Since no official patch is currently available for the affected theme versions (up to 1.0.14), it is critical to implement this mitigation to prevent exploitation.

Other recommended steps include:

  • Temporarily disabling or removing the vulnerable Artrium theme if possible.
  • Restricting file permissions on the server to limit access to sensitive files.
  • Monitoring logs closely for any signs of exploitation attempts.
  • Implementing or enhancing web application firewall (WAF) rules to block suspicious requests.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart