CVE-2026-22410
Local File Inclusion Vulnerability in Mikado-Themes Dolcino
Publication date: 2026-03-05
Last updated on: 2026-03-09
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mikado-themes | dolcino | 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-22410 is a Local File Inclusion (LFI) vulnerability in the WordPress Dolcino Theme versions up to and including 1.6. It allows an unauthenticated attacker to include and display local files from the target website by exploiting improper control of filename for include/require statements in PHP.
This vulnerability is classified under OWASP Top 10 A3: Injection and can be exploited without any authentication.
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'Exploiting this vulnerability could expose sensitive files on the target website, such as those containing database credentials.'}, {'type': 'paragraph', 'content': "This exposure can potentially lead to a complete database takeover depending on the site's configuration."}, {'type': 'paragraph', 'content': 'The vulnerability has a high severity score (CVSS 8.1), indicating a highly dangerous risk that is expected to be exploited in the wild.'}] [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 allows an unauthenticated attacker to include and display local files via the WordPress Dolcino Theme up to version 1.6. Detection can involve monitoring for suspicious HTTP requests attempting to exploit Local File Inclusion (LFI) by including unexpected file paths or parameters in URLs.'}, {'type': 'paragraph', 'content': 'Common detection methods include inspecting web server logs for requests containing suspicious include or require parameters, such as attempts to access sensitive files like /etc/passwd or configuration files.'}, {'type': 'list_item', 'content': "Use command-line tools like grep to search web server logs for suspicious patterns, for example: grep -i 'include' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "Look for URL parameters that may be used to exploit LFI, such as: curl -v 'http://example.com/?page=../../../../etc/passwd'"}, {'type': 'list_item', 'content': 'Employ web application firewalls or intrusion detection systems with rules targeting LFI attempts, such as the Patchstack mitigation rule for this vulnerability.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Since no official patch is currently available for this vulnerability, immediate mitigation involves applying the Patchstack mitigation rule that blocks attacks exploiting this Local File Inclusion vulnerability.
Users are advised to promptly implement this mitigation to secure their websites until an official patch can be developed, tested, and safely applied.
Additional general mitigation steps include restricting file permissions to limit access to sensitive files, disabling unnecessary PHP functions that allow file inclusion, and monitoring web traffic for suspicious activity.