CVE-2026-27047
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 Curly Core curly-core allows PHP Local File Inclusion.This issue affects Curly Core: from n/a through <= 2.1.6.
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 confidenceMikado-Themes Curly Core plugin contains a Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in PHP include/require statements without sufficient validation, allowing attackers to include arbitrary local files. The vulnerability exists in curly-core versions through 2.1.6.
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 Curly Core installationLocate the Curly Core theme or plugin files on the server. Check the wp-content/themes/ or wp-content/plugins/ directory for folders named 'curly-core', 'mikado-curly', or similar Curly theme components. Also check for any custom post type or shortcode modules that may include external files.Affected if Curly Core theme or plugin files are present on the server.
-
Determine installed versionOpen the main Curly Core plugin or theme file (typically version.php, style.css, or the main plugin header file) and locate the version constant or comment header. Compare the version number against the affected range <= 2.1.6.Affected if The installed version is 2.1.6 or lower.
-
Locate file inclusion codeSearch the Curly Core directory for PHP include, require, include_once, or require_once statements that process user-supplied parameters. Look for patterns like include($_GET['...']) or require($variable) in files within the includes/ or shortcodes/ folders. Identify which parameters accept file paths.Affected if File inclusion code that uses unsanitized user input is found in the Curly Core codebase.
-
Check URL parameter exposureIdentify which HTTP request parameters feed into the file inclusion functions found in the previous step. Determine if these parameters are accessible via URL query strings or POST data without authentication or validation.Affected if User-controlled parameters are passed directly to include/require statements and are reachable via HTTP requests.
-
Test for directory traversalManually send HTTP requests with directory traversal sequences (e.g., ../../../../etc/passwd) in the identified vulnerable parameters. Check if the server returns file contents instead of an error or validation message.Affected if The server returns the contents of files outside the intended directory when traversal sequences are used.
The environment is affected if Curly Core version 2.1.6 or lower is installed AND the vulnerable file inclusion functionality is exposed to user input, allowing directory traversal sequences to read arbitrary local files.
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 curly-core to the latest version that includes patched code with proper input validation and sanitization on all file inclusion functions. If no update is available, implement web application firewall rules to block directory traversal patterns in request parameters.
- 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-27047 — 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-27047 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