CVE-2026-27077
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 MultiOffice multioffice allows PHP Local File Inclusion.This issue affects MultiOffice: from n/a through <= 1.2.
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 (LFI) vulnerability exists in the Mikado-Themes MultiOffice theme (versions up to 1.2) due to improper control of filename parameters in include/require statements, allowing attackers to include arbitrary files from the server file system.
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 MultiOffice theme installationLocate the theme files on the web server. Check the theme's version.php or style.css file typically found in wp-content/themes/mikado-multioffice/ or similar paths depending on the CMS platform. Look for version declaration strings.Affected if The MultiOffice theme by Mikado-Themes is installed and the version is 1.2 or lower
-
Determine the installed theme versionOpen the theme's version file (commonly version.php, style.css header, or theme.yml) and locate the version number. Compare it against the affected range: versions up to and including 1.2 are vulnerable.Affected if The installed version is 1.2 or any earlier version of the MultiOffice theme
-
Locate file inclusion code in theme filesSearch theme PHP files for dynamic include/require statements that use variables or request parameters without sanitization. Look for patterns like 'include($_GET[...])', 'require($file)', 'include($path)', or similar unsanitized variable usage in include/require functions.Affected if The theme contains include/require statements using unsanitized user input (GET, POST, or cookie parameters) as file paths
-
Verify input validation on file inclusion functionsReview the PHP code handling file inclusion within the theme. Check if filename parameters are validated against a whitelist, sanitized with basename(), or otherwise strictly controlled before being used in include/require statements.Affected if No input validation, sanitization, or whitelisting is performed on file path parameters before inclusion
-
Check PHP configuration for dangerous settingsReview the php.ini configuration file. Check the values of allow_url_include (should be Off) and open_basedir restrictions. While LFI typically does not require URL includes, these settings indicate overall security posture.Affected if allow_url_include is enabled and no open_basedir restrictions are in place (this alone does not confirm LFI but indicates higher risk)
You are affected if the MultiOffice theme version 1.2 or lower is installed AND the theme contains unsanitized file inclusion logic using include/require with dynamic file paths.
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 a patched version of the MultiOffice theme; if unavailable, implement strict input validation/whitelisting on file inclusion functions and disable allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27077 — 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-27077 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