CVE-2026-22418
Local File Inclusion in Great Lotus PHP
Publication date: 2026-03-05
Last updated on: 2026-03-10
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ancorathemes | great_lotus | to 1.3.1 (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-22418 is a Local File Inclusion (LFI) vulnerability found in the WordPress Great Lotus Theme versions up to and including 1.3.1.
This vulnerability allows an unauthenticated attacker to include and display local files from the target website by exploiting improper control of filename parameters in PHP include/require statements.
As a result, sensitive information such as database credentials can be exposed.
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'Exploitation of this vulnerability can lead to the exposure of sensitive files on the server, including database credentials.'}, {'type': 'paragraph', 'content': "Depending on the website's configuration, an attacker could potentially take over the entire database."}, {'type': 'paragraph', 'content': 'Since no authentication is required to exploit this flaw, the risk and likelihood of attack are high.'}] [1]
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?
[{'type': 'paragraph', 'content': 'This vulnerability is a Local File Inclusion (LFI) issue in the WordPress Great Lotus Theme versions up to 1.3.1 that allows unauthenticated attackers to include and display local files. Detection typically involves monitoring for suspicious HTTP requests attempting to exploit file inclusion, such as requests containing file path traversal patterns or attempts to include sensitive files.'}, {'type': 'paragraph', 'content': 'While no specific commands are provided in the available resources, common detection methods include inspecting web server logs for unusual URL parameters that reference local files, for example, using grep to search for suspicious patterns in access logs.'}, {'type': 'list_item', 'content': 'grep -iE "(\\.|%2e){2,}/" /var/log/apache2/access.log'}, {'type': 'list_item', 'content': 'grep -i "include" /var/log/apache2/access.log'}, {'type': 'paragraph', 'content': 'Additionally, monitoring for unexpected file inclusion attempts or anomalous web requests targeting the Great Lotus theme endpoints can help detect exploitation attempts.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Since no official patch is currently available for this vulnerability, immediate mitigation involves implementing the Patchstack mitigation rule designed to block attacks targeting this Local File Inclusion flaw.
Users are strongly advised to apply this mitigation rule as soon as possible to protect their websites from exploitation.
Other general mitigation steps include restricting file inclusion permissions, disabling remote file inclusion if enabled, and monitoring web traffic for suspicious activity.