CVE-2026-27079
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 Amfissa amfissa allows PHP Local File Inclusion.This issue affects Amfissa: from n/a through <= 1.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 confidenceA Local File Inclusion (LFI) vulnerability exists in the Mikado-Themes Amfissa theme (version 1.1 and below) where PHP include/require statements improperly handle user-controllable filename parameters, allowing attackers to read sensitive local files on the server.
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 Amfissa theme installationLocate the theme directory in your WordPress or CMS installation. Look for a folder named 'amfissa', 'mikado-amfissa', or check wp-content/themes for Mikado theme folders.Affected if The Amfissa theme directory exists in the themes folder
-
Determine installed theme versionOpen the theme's style.css file (usually in the theme root) and locate the 'Version:' header in the CSS comment block at the top, or check theme.json for a version field.Affected if The version is 1.1 or lower, or if no version is declared and the theme appears to be the Amfissa theme
-
Locate PHP files with include/require statementsSearch the theme directory for PHP files containing 'include(', 'require(', 'include_once(', or 'require_once(' statements. Use grep or manually inspect common template files like header.php, footer.php, and any files in subdirectories.Affected if PHP files contain include/require statements that reference variables without sanitization
-
Inspect file inclusion parameters for user inputExamine the include/require statements found and trace whether any parameters (such as 'file', 'page', 'template', 'path', or similar) come directly from user request data like $_GET, $_POST, or $_REQUEST without validation.Affected if User-controllable parameters are passed directly to include/require without validation or sanitization
-
Verify vulnerable endpoints are accessibleTest accessing common entry points that might pass parameters to file inclusion functions (e.g., URLs with ?file= or ?page= query parameters). Check if the application responds to these parameters.Affected if URL parameters like ?file= or ?template= are processed by the theme and can be manipulated to traverse directories
Your environment is affected if the Amfissa theme version 1.1 or below is installed and user-controllable parameters are passed to PHP include/require statements without validation.
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 dataImplement strict input validation using whitelist filtering for file inclusion paths, use basename() to strip directory traversal sequences, and avoid passing user input directly to include/require statements.
- 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-27079 — 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-27079 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