CVE-2026-27075
Local File Inclusion Vulnerability in Mikado-Themes Belfort
Publication date: 2026-03-25
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mikado-themes | belfort | to 1.0 (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
How can this vulnerability impact me? :
Exploitation of this vulnerability can expose sensitive information such as database credentials by allowing attackers to read local files on the server.
Depending on the website's configuration, this could lead to a complete database takeover.
The vulnerability has a high severity score (CVSS 8.1) and is often targeted in mass-exploit campaigns, putting affected websites at significant risk.
Can you explain this vulnerability to me?
CVE-2026-27075 is a Local File Inclusion (LFI) vulnerability in the WordPress Belfort Theme versions up to and including 1.0. It allows unauthenticated attackers to include local files from the target website and display their contents.
This happens due to improper control of the filename used in PHP include/require statements, which can be exploited to access sensitive files on the server.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability allows unauthenticated attackers to include local files from the target website and display their contents, which can be detected by monitoring for suspicious HTTP requests attempting to exploit Local File Inclusion (LFI) patterns.
Common detection methods include inspecting web server logs for requests containing suspicious parameters that reference local files, such as those including directory traversal sequences (e.g., ../) or attempts to include sensitive files like /etc/passwd or configuration files.
While no specific commands are provided in the resources, typical commands to detect such activity might include using grep on web server logs to find suspicious patterns, for example:
- grep -iE "(\.{2}/|etc/passwd|config)" /var/log/apache2/access.log
- tail -f /var/log/nginx/access.log | grep 'include' or 'require'
Additionally, network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to detect and alert on such LFI attack patterns.
What immediate steps should I take to mitigate this vulnerability?
Since no official patch is currently available for the Belfort Theme, immediate mitigation steps include applying the mitigation rule released by Patchstack that can block attacks exploiting this vulnerability.
Users are advised to update the affected theme if an update becomes available or seek assistance from their hosting provider or web developer to implement these mitigations.
Additional general mitigation steps include:
- Implementing a Web Application Firewall (WAF) to block malicious requests targeting LFI vulnerabilities.
- Restricting file permissions on the server to limit access to sensitive files.
- Disabling PHP functions that allow file inclusion if not needed.
- Monitoring logs for suspicious activity and responding promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The Local File Inclusion (LFI) vulnerability in the Belfort WordPress Theme can lead to unauthorized access to sensitive information such as database credentials. This exposure can result in a complete database takeover depending on the website's configuration.
Such unauthorized access and potential data breaches could negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data from unauthorized disclosure.
However, the provided information does not explicitly detail the direct effects on compliance or specific regulatory implications.