CVE-2026-27076
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 LuxeDrive luxedrive allows PHP Local File Inclusion.This issue affects LuxeDrive: 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 LuxeDrive theme (version <= 1.0) where PHP include/require statements do not properly validate user-supplied input, allowing attackers to include arbitrary local PHP files. This can lead to code execution, sensitive data exposure, or further attack escalation.
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 LuxeDrive theme is installedLocate the theme directory - typically in wp-content/themes/luxedrive/ or wp-content/themes/ luxe-drive/ - and list its contents to verify the theme existsAffected if The LuxeDrive theme by Mikado-Themes is present in the WordPress themes directory
-
Identify the installed theme versionOpen the theme's style.css file in the theme root and look for the 'Version:' comment in the file header, or check functions.php for a version constantAffected if The version cannot be determined or is prior to any patched release
-
Locate include/require statements with user inputSearch all PHP files in the theme directory for patterns like include($_GET, require($_POST, include_once($_REQUEST - use grep or a code search tool across all .php files in the theme folderAffected if Any PHP file contains include/require statements that directly use unsanitized superglobal array values (GET, POST, REQUEST, COOKIE)
-
Inspect the specific vulnerable code locationManually review PHP files in any 'include' or 'lib' subdirectories for dynamic file inclusion that lacks basename() wrapping or allowlist validation on user-supplied parametersAffected if User-controlled parameters are used in include/require without sanitization such as basename() or allowlist validation
-
Test for LFI via HTTP parametersIf identified, attempt to include a known safe file using a parameter value like ../../../../wp-config.php or ../../etc/passwd (in a non-production test environment only) to confirm the vulnerability existsAffected if The application returns content from files outside the intended include path or displays file contents in the response
You are affected if the LuxeDrive theme is installed and contains PHP code with include/require statements using unsanitized user input from GET, POST, or REQUEST superglobals.
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 an allowlist approach for any file inclusion, avoid using user input directly in include/require statements, and ensure PHP configuration disables allow_url_include.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27076 — 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-27076 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