CVE-2026-27075
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 Belfort belfort allows PHP Local File Inclusion.This issue affects Belfort: 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 · high confidenceA PHP Local File Inclusion vulnerability exists in the Belfort theme by Mikado-Themes where user-supplied input is used in include/require statements without proper validation. This allows attackers to potentially read sensitive files or execute arbitrary PHP code 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.
-
Locate Belfort theme filesSearch the web root directory for files belonging to the Belfort theme by Mikado-Themes. Common paths include /wp-content/themes/belfort/ (if WordPress) or /themes/belfort/. Look for files like header.php, footer.php, or any custom PHP files in the theme directory.Affected if The Belfort theme directory exists on the server and is actively loaded by the web application.
-
Determine theme versionCheck for a style.css or theme.json file within the Belfort theme directory. Open the file and look for a 'Version:' header or 'version' field. Compare this version to any known versions (note: the theme appears to have no version beyond 1.0).Affected if The installed version is the Belfort theme by Mikado-Themes, regardless of version number.
-
Identify include/require statements using user inputIn the Belfort theme directory, search all PHP files for patterns like 'include($_GET[', 'require($_GET[', 'include($_POST[', 'require($_POST[', or similar where $_GET, $_POST, $_REQUEST, or $_COOKIE superglobals are used directly in include/require statements without sanitization.Affected if Any PHP file in the theme contains include/require statements that incorporate unsanitized user-supplied input from request parameters.
-
Verify vulnerable code is accessibleIf suspicious include/require patterns are found, test whether the affected parameters (e.g., a specific query string parameter used in the include) can be passed via HTTP requests. Attempt to manipulate the parameter to include a known file path (e.g., ../../wp-config.php for WordPress) to confirm the LFI is exploitable.Affected if The vulnerable include/require parameter is exposed via URL or form input and allows path traversal (e.g., using ../ to access files outside the theme directory).
A user is affected if the Belfort theme by Mikado-Themes is installed and any PHP file in the theme uses include/require with 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 dataSince the Belfort theme appears to be abandoned (no version beyond 1.0), the recommended remediation is to replace or remove the theme entirely; if continued use is required, locate and sanitize all include/require statements to validate file paths against an allowlist.
- 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-27075 — 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-27075 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