Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22412: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Mikado-Themes Eona

0
Unknown
VulnerabilityCVE-2026-22412cvecve-2026-22412
Published: Thu Mar 05 2026 (03/05/2026, 05:53:36 UTC)
Source: CVE Database V5
Vendor/Project: Mikado-Themes
Product: Eona

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes Eona eona allows PHP Local File Inclusion.This issue affects Eona: from n/a through <= 1.3.

AI-Powered Analysis

AILast updated: 03/05/2026, 09:00:03 UTC

Technical Analysis

CVE-2026-22412 is a Local File Inclusion (LFI) vulnerability found in Mikado-Themes Eona, a WordPress theme product, affecting versions up to and including 1.3. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, which allows an attacker to manipulate the file path and include arbitrary local files on the web server. This can lead to disclosure of sensitive files such as configuration files, password files, or application source code, and potentially enable remote code execution if combined with other vulnerabilities or misconfigurations. The vulnerability is classified as an LFI rather than Remote File Inclusion (RFI), indicating that remote URLs cannot be included, but local files on the server can be accessed. No CVSS score has been assigned yet, and no public exploits have been reported, but the flaw is publicly disclosed and considered serious. The vulnerability affects websites using the Eona theme, which is part of the Mikado-Themes portfolio, commonly used in WordPress CMS deployments. The root cause is insufficient validation or sanitization of user-supplied input controlling the include/require filename, allowing directory traversal or arbitrary file inclusion. The issue was reserved in early 2026 and published in March 2026. No official patches or fixes are linked yet, so users must monitor vendor updates or apply manual mitigations.

Potential Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive information stored on the web server, such as configuration files containing database credentials, user data, or internal application logic. Attackers exploiting this flaw can gain insights into the server environment, which can facilitate further attacks like privilege escalation or remote code execution. In some cases, LFI vulnerabilities can be chained with other vulnerabilities to achieve full system compromise. For organizations, this can lead to data breaches, service disruption, reputational damage, and regulatory penalties. Since the vulnerability affects a WordPress theme, it potentially impacts a wide range of websites, including small businesses, e-commerce platforms, and corporate sites. The lack of authentication requirement and ease of exploitation through crafted HTTP requests increase the risk. Although no active exploits are known, the public disclosure means attackers may develop exploits soon, increasing urgency for mitigation.

Mitigation Recommendations

Organizations using Mikado-Themes Eona should immediately audit their installations to determine if they use affected versions (up to 1.3). Until an official patch is released, apply the following mitigations: 1) Implement strict input validation and sanitization on all parameters controlling file inclusion to restrict allowed filenames to a safe whitelist or fixed values. 2) Disable PHP functions that allow file inclusion from user input if possible or use PHP configuration directives to restrict file access (e.g., open_basedir). 3) Employ Web Application Firewalls (WAFs) with rules to detect and block suspicious file inclusion attempts and directory traversal patterns. 4) Monitor web server logs for unusual requests targeting include/require parameters. 5) Keep WordPress core, plugins, and themes up to date and subscribe to vendor security advisories for timely patching. 6) Consider isolating the web server environment and limiting file permissions to reduce the impact of potential exploitation. 7) Conduct security testing, including code review and penetration testing, focusing on file inclusion vectors.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2026-01-07T12:21:56.449Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a92043d1a09e29cbe6975f

Added to database: 3/5/2026, 6:18:43 AM

Last enriched: 3/5/2026, 9:00:03 AM

Last updated: 3/5/2026, 3:03:34 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses