CVE-2026-39538
Local File Inclusion Vulnerability in Mikado Core
Publication date: 2026-04-08
Last updated on: 2026-04-14
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mikado-themes | mikado_core | to 1.6 (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-39538 is a Local File Inclusion (LFI) vulnerability in the Mikado Core WordPress plugin versions up to 1.6. It allows an attacker with at least contributor or developer privileges to include and display local files from the target website.
This improper control of filename for include/require statements in PHP can expose sensitive information such as database credentials.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The Local File Inclusion vulnerability in Mikado Core Plugin versions up to 1.6 allows attackers to access sensitive information such as database credentials, which could lead to a complete database takeover depending on the website's configuration.
Exposure of sensitive data due to this vulnerability can result in non-compliance with data protection regulations like GDPR and HIPAA, as these standards require adequate protection of personal and sensitive information against unauthorized access.
Therefore, failing to patch this vulnerability could lead to violations of such regulations, potentially resulting in legal and financial consequences.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can access and display local files on the website, potentially exposing sensitive data like database credentials.
Depending on the website's configuration, this exposure could lead to a complete database takeover.
The vulnerability has a CVSS severity score of 7.5, indicating a significant risk, and is classified under the OWASP Top 10 category A3: Injection.
Although rated as low severity by Patchstack priority, such vulnerabilities are commonly exploited in mass campaigns targeting many websites.
Users are strongly advised to update to version 2.2.2 or later to mitigate this risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability affects Mikado Core Plugin versions up to 1.6 and allows Local File Inclusion (LFI) by users with contributor or developer privileges. Detection can involve checking the plugin version installed on your WordPress site.
To detect if your system is vulnerable, you can verify the plugin version by running commands to list installed WordPress plugins and their versions.
- Use WP-CLI command: wp plugin list | grep mikado-core to check the installed version of the Mikado Core plugin.
- Inspect web server logs for suspicious requests attempting to include local files via URL parameters related to the Mikado Core plugin.
- Look for unusual PHP errors or warnings in the logs that may indicate attempts to exploit Local File Inclusion.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the Mikado Core plugin to version 2.2.2 or later, where this vulnerability has been patched.
If immediate updating is not possible, restrict contributor and developer privileges to trusted users only, as exploitation requires at least these privilege levels.
Consider using security plugins or web application firewalls that can detect and block Local File Inclusion attempts.
Monitor your website and server logs for any suspicious activity related to file inclusion attempts.