Mikado-Themes Curly Core Plugin up to 2.1.6 on WordPress filename control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.58 |
Summary
A vulnerability categorized as critical has been discovered in Mikado-Themes Curly Core Plugin up to 2.1.6 on WordPress. The impacted element is an unknown function. The manipulation results in filename control. This vulnerability is reported as CVE-2026-27047. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in Mikado-Themes Curly Core Plugin up to 2.1.6 on WordPress. It has been classified as critical. Affected is an unknown functionality. The manipulation with an unknown input leads to a filename control vulnerability. CWE is classifying the issue as CWE-98. The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was disclosed by Tran Nguyen Bao Khanh. The advisory is available at patchstack.com. This vulnerability is traded as CVE-2026-27047 since 02/17/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/01/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 8.1
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Filename controlCWE: CWE-98
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/17/2026 CVE reserved03/25/2026 Advisory disclosed
03/25/2026 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Tran Nguyen Bao Khanh
Status: Not defined
CVE: CVE-2026-27047 (🔒)
GCVE (CVE): GCVE-0-2026-27047
GCVE (VulDB): GCVE-100-353382
Entry
Created: 03/25/2026 19:56Updated: 04/01/2026 02:35
Changes: 03/25/2026 19:56 (54), 04/01/2026 02:35 (12)
Complete: 🔍
Cache ID: 216:AB4:103
No comments yet. Languages: en.
Please log in to comment.