CVE-2026-27078
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 Emaurri emaurri allows PHP Local File Inclusion.This issue affects Emaurri: from n/a through <= 1.0.1.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Mikado-Themes Emaurri theme that allows attackers to manipulate file inclusion statements to execute arbitrary PHP code or access sensitive files on the server. The vulnerability stems from improper control of filenames in include/require statements, likely due to insufficient input validation on user-controlled parameters.
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.
-
Confirm Emaurri theme installationLocate theme files in the web root - typically under wp-content/themes/emaurri for WordPress or the themes directory of the respective CMS. Check for theme.json or style.css containing 'Emaurri' or 'Mikado' themename.Affected if The Mikado-Themes Emaurri theme is present in the environment
-
Determine the installed theme versionOpen the theme's style.css file or theme.json and locate the Version: header field. Compare this version number against any official patched releases from MikadoThemes.Affected if The installed version is older than the patched version or cannot be determined
-
Find file inclusion code using user inputSearch all PHP files in the theme directory for patterns: include($_, require($_, include_once($_, require_once( - especially where $_GET, $_POST, or $_REQUEST parameters are passed directly to these functions.Affected if Unsanitized user-supplied parameters are used in include/require statements
-
Check for proper input validation on include parametersReview the identified file inclusion code for validation functions such as basename(), realpath(), or allowlist checks before including files. Look for code that validates or restricts the parameter to expected values.Affected if No validation, weak validation, or direct user input is used in file inclusion functions without sanitization
-
Identify accessible entry pointsDetermine if any scripts using vulnerable include/require patterns are web-accessible (in public directories) and accept parameters via GET or POST requests without authentication.Affected if Vulnerable file inclusion code is reachable via HTTP/HTTPS requests without require authentication
The environment is affected if the Mikado-Themes Emaurri theme is installed and its PHP code contains file inclusion statements that use unsanitized user input without proper validation or authentication controls.
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 dataUpgrade to the latest patched version of the Emaurri theme; if no patch is available, implement strict input validation and allowlist controls on all file inclusion parameters, or disable PHP execution in upload directories.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27078 — 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-27078 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