CVE-2026-27080
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 Deston deston allows PHP Local File Inclusion.This issue affects Deston: from n/a through <= 1.0.
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 Local File Inclusion (LFI) vulnerability exists in the Mikado-Themes Deston theme where user-controlled input is not properly validated before being used in PHP include/require statements. This allows attackers to include arbitrary PHP files from the server file system, 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.
-
Locate Deston theme installationSearch the web server document root for the 'deston' or 'Deston' theme directory, typically under wp-content/themes/ for WordPress or similar theme directories for other PHP applicationsAffected if The Deston theme by Mikado-Themes is found in the environment
-
Determine installed theme versionOpen the theme's main style.css or functions.php file and look for a version comment or $theme_version variable, then compare against '1.0' and earlier versionsAffected if The theme version is 1.0 or any version prior to 1.0
-
Identify PHP include/require usageGrep the theme directory for patterns like 'include(', 'require(', 'include_once(', 'require_once(' followed by variables (e.g., $file, $page, $template) that could contain user inputAffected if The theme contains include or require statements using variable parameters without sanitization
-
Check for unprotected file path parametersExamine the identified include/require calls to determine if parameters come from $_GET, $_POST, or $_REQUEST superglobals without validation via basename() or whitelist checksAffected if User-supplied input from request parameters flows directly to file inclusion functions without sanitization
-
Verify parameter accessibilityAttempt to access the identified vulnerable parameters via URL query strings (e.g., ?file=../../wp-config.php) to confirm they are reachable without authenticationAffected if The vulnerable parameters are accessible via HTTP requests and accept path traversal sequences
The environment is affected if the Mikado-Themes Deston theme version 1.0 or earlier is installed AND the theme contains include/require statements using unsanitized user input that is accessible via HTTP requests.
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 dataUpdate the Deston theme to the latest patched version. If no update is available, implement strict input validation on all file inclusion parameters and consider using allowlists for permitted files.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27080 — 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-27080 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