Mikado-mes Biagiotti Core Plugin up to 2.1.1 on WordPress file inclusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.52 |
Summary
A vulnerability marked as problematic has been reported in Mikado-mes Biagiotti Core Plugin up to 2.1.1. This affects an unknown part. Performing a manipulation results in file inclusion. This vulnerability is cataloged as CVE-2026-66657. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Mikado-mes Biagiotti Core Plugin up to 2.1.1. It has been classified as problematic. This affects an unknown code. The manipulation with an unknown input leads to a file inclusion vulnerability. CWE is classifying the issue as CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. This is going to have an impact on confidentiality. The summary by CVE is:
Unauthenticated Local File Inclusion in Biagiotti Core <= 2.1.1 versions.
The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-66657 since 07/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/13/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: File inclusionCWE: CWE-73
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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
07/27/2026 CVE reserved08/13/2026 Advisory disclosed
08/13/2026 VulDB entry created
08/13/2026 VulDB entry last update
Sources
Advisory: patchstack.comStatus: Not defined
CVE: CVE-2026-66657 (🔒)
GCVE (CVE): GCVE-0-2026-66657
GCVE (VulDB): GCVE-100-389589
Entry
Created: 08/13/2026 17:38Changes: 08/13/2026 17:38 (53)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.