Skip to main content
Vulnerability Database/CVE-2026-27047

CVE-2026-27047: Curly Core PHP File Inclusion Vulnerability

CVE-2026-27047 is a PHP local file inclusion vulnerability in Mikado-Themes Curly Core plugin that enables attackers to include malicious files. This article covers the technical details, affected versions, and mitigation.

Updated:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-27047 Overview

CVE-2026-27047 is a PHP Local File Inclusion (LFI) vulnerability affecting the Mikado-Themes Curly Core WordPress plugin. The flaw stems from improper control of filename arguments used in PHP include or require statements [CWE-98]. The vulnerability impacts all versions of Curly Core up to and including 2.1.6. An unauthenticated attacker can manipulate file path parameters to cause the plugin to load arbitrary local files on the server. Successful exploitation can result in source code disclosure, exposure of sensitive configuration data, and code execution if attackers can stage controlled content through other channels such as log poisoning or file uploads.

Critical Impact

Unauthenticated attackers can include arbitrary local PHP files, leading to information disclosure and potential remote code execution on affected WordPress sites.

Affected Products

  • Mikado-Themes Curly Core plugin versions up to and including 2.1.6
  • WordPress installations running the curly-core plugin
  • Sites using themes that bundle the Curly Core companion plugin

Discovery Timeline

  • 2026-03-25 - CVE-2026-27047 published to NVD
  • 2026-04-24 - Last updated in NVD database

Technical Details for CVE-2026-27047

Vulnerability Analysis

The vulnerability is classified under [CWE-98], Improper Control of Filename for Include/Require Statement in PHP Program. The Curly Core plugin accepts user-controlled input and passes it to a PHP file inclusion function without sufficient validation or sanitization. This allows attackers to traverse the file system and load files outside the intended directory. The Patchstack advisory categorizes the issue as PHP Local File Inclusion, indicating the inclusion is restricted to files already present on the host. The attack is launched over the network, requires no authentication, and needs no user interaction. The high attack complexity reflects conditions such as path normalization or input filtering that an attacker must work around.

Root Cause

The root cause is the use of unvalidated request input as part of a PHP include, include_once, require, or require_once statement. The plugin fails to enforce an allowlist of permitted template or module names. It also fails to canonicalize paths and reject directory traversal sequences such as ../. Because PHP resolves the included file at runtime, any readable file on the server may be executed in the PHP interpreter context.

Attack Vector

An unauthenticated remote attacker sends a crafted HTTP request to a Curly Core endpoint that accepts a file or template parameter. By supplying a relative path with traversal sequences or an absolute path, the attacker forces inclusion of an arbitrary local file. Targets commonly include wp-config.php, log files seeded with PHP payloads, session files, and temporary upload locations. When combined with log poisoning or writable file primitives, LFI escalates to full remote code execution under the web server account.

The vulnerability is described in prose only because no verified proof-of-concept code has been published. See the Patchstack Curly Core Plugin Advisory for additional technical context.

Detection Methods for CVE-2026-27047

Indicators of Compromise

  • HTTP requests to Curly Core plugin endpoints containing path traversal sequences such as ../, ..%2f, or encoded null bytes in query parameters
  • Web server access log entries referencing sensitive files such as wp-config.php, /etc/passwd, or /proc/self/environ in plugin request parameters
  • Unexpected PHP error log entries indicating failed include or require calls with attacker-controlled paths
  • Outbound network connections initiated by the php-fpm or web server process shortly after suspicious LFI requests

Detection Strategies

  • Inspect WordPress request logs for parameters passed to wp-content/plugins/curly-core/ paths that contain filesystem path syntax
  • Deploy web application firewall rules that flag directory traversal patterns and PHP wrapper schemes such as php://filter and data://
  • Correlate plugin requests with subsequent file reads of sensitive WordPress configuration files using endpoint telemetry
  • Hunt for new or modified PHP files in wp-content/uploads/ that could serve as second-stage payloads for LFI chaining

Monitoring Recommendations

  • Enable verbose access logging on WordPress front-end web servers and ship logs to a centralized analytics platform
  • Monitor process lineage from php-fpm or apache2 for unexpected child processes that may indicate post-exploitation activity
  • Track file integrity on the WordPress installation directory, especially wp-config.php and plugin folders
  • Alert on anomalous outbound traffic from web servers, which can indicate data exfiltration following LFI exploitation

How to Mitigate CVE-2026-27047

Immediate Actions Required

  • Identify all WordPress sites running the Mikado-Themes Curly Core plugin and inventory installed versions
  • Disable the Curly Core plugin until a patched version is verified and installed, particularly on internet-facing sites
  • Deploy WAF rules that block directory traversal and PHP wrapper schemes targeting curly-core request paths
  • Review web server and PHP error logs for prior exploitation attempts against affected endpoints

Patch Information

As of the last NVD update on 2026-04-24, the advisory indicates the vulnerability affects Curly Core through version 2.1.6. Administrators should consult the Patchstack Curly Core Plugin Advisory for the latest fixed version and update to a patched release as soon as it is published by Mikado-Themes.

Workarounds

  • Remove or deactivate the Curly Core plugin if it is not essential to site functionality
  • Restrict access to plugin endpoints via web server rules or .htaccess directives until a patch is applied
  • Set open_basedir in PHP configuration to confine file inclusion to the WordPress installation directory
  • Run the PHP process under a least-privileged account that cannot read sensitive system files such as /etc/passwd
bash
# Example php.ini hardening to limit LFI impact
open_basedir = "/var/www/html/:/tmp/"
allow_url_include = Off
allow_url_fopen = Off

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.