LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27047: WordPress Curly Core plugin <= 2.1.6 - Local File Inclusion vulnerability

Improper 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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27047 affects the WordPress Curly Core plugin through version 2.1.6. It can allow an attacker to include local files through improper filename handling in PHP. The published CVSS score is 8.1, reflecting potential confidentiality, integrity, and availability impact if successfully exploited.

Executive priority

Treat this as a high-priority WordPress plugin issue for any site using Curly Core. Prioritize inventory first, because urgency depends on whether the plugin is present. No source-provided evidence confirms active exploitation or an available patch.

Technical view

The issue is categorized as CWE-98 in Mikado-Themes Curly Core. The CVE description calls it PHP Local File Inclusion, while the CWE label references include/require filename control. CVSS 3.1 is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning remote, unauthenticated exploitation is modeled but with high attack complexity.

Likely exposure

Exposure is likely limited to WordPress sites running Mikado-Themes Curly Core plugin version 2.1.6 or earlier. The supplied data does not identify other affected products, bundled distributions, or a fixed version.

Exploitation context

The CVE is not listed as KEV in the supplied data, and no cited source states active exploitation. The CVSS vector indicates no authentication or user interaction is required, but attack complexity is high.

Researcher notes

Source evidence is limited. The record describes LFI, while the CWE title references PHP Remote File Inclusion terminology. Do not assume exploitability details beyond the CVSS vector. No patch version, proof of exploitation, or workaround is named in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the Curly Core plugin and installed version.
  • If running version 2.1.6 or earlier, check vendor or Patchstack guidance immediately.
  • Disable or remove the plugin if it is not business-critical.
  • Apply any vendor-confirmed fixed release when available and tested.
  • Monitor web logs for unusual requests involving Curly Core plugin paths.

Validation and detection

  • Confirm whether Curly Core is installed on each WordPress site.
  • Record the plugin version and compare it against affected versions through 2.1.6.
  • Check Patchstack and the CVE record for updated remediation details.
  • Review web access logs for suspicious plugin-targeted requests.
  • Verify compensating controls after any disablement, removal, or update.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27047 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-27047Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Mikado-ThemesCurly Corecurly-core, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.