CVE-2026-22394
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes Evently evently allows PHP Local File Inclusion.This issue affects Evently: from n/a through <= 1.7.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA PHP Local File Inclusion vulnerability exists in the Mikado-Themes Evently theme (versions up to 1.7) where user-supplied input is improperly used in include/require statements without sufficient validation. This allows attackers to include arbitrary PHP files from the server, potentially leading to code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the Evently theme is installedLocate the theme directory (typically wp-content/themes/mikado-evently or similar) and check the style.css or theme.json file for the version numberAffected if The installed version is 1.7 or lower
-
Search for dynamic file inclusion callsGrep the theme's PHP files for include, require, include_once, or require_once statements that use variables or parameters without sanitizationAffected if Files contain include/require statements using $_GET, $_POST, or $_REQUEST variables directly
-
Identify parameters used in include/requireExamine any include/require statements found and trace back whether user-controlled parameters (from URL or form input) flow into these calls without validationAffected if User-supplied input from request parameters reaches include/require without basename() or realpath() checks
-
Test for LFI with benign inputIf vulnerable parameters are identified, attempt to include a known safe file (such as a configuration file in the theme directory) using the suspected parameterAffected if The server returns content from the included file, confirming the LFI exists
-
Check web server logs for exploitation attemptsReview access logs for patterns where include/require parameters reference PHP files outside the theme directoryAffected if Logs show requests with directory traversal sequences (../) or attempts to include sensitive PHP files
A user is affected if they are running the Evently theme version 1.7 or lower AND their theme code contains include/require statements that accept unvalidated user input from request parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataFix requires implementing strict input validation on any parameters used in include/require statements—use allowlisting, basename(), and realpath() sanitization, or refactor to avoid direct user input in file inclusion functions.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22394 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22394 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data