Fiorello Plugin up to 1.0 on WordPress resource injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Fiorello Plugin up to 1.0 on WordPress. The affected element is an unknown function. Performing a manipulation results in resource injection. This vulnerability is cataloged as CVE-2026-22396. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Fiorello Plugin up to 1.0 on WordPress. It has been classified as critical. This affects some unknown functionality. The manipulation with an unknown input leads to a resource injection vulnerability. CWE is classifying the issue as CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Authorization Bypass Through User-Controlled Key vulnerability in Mikado-Themes Fiorello fiorello allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Fiorello: from n/a through <= 1.0.
It is possible to read the advisory at wordfence.com. This vulnerability is uniquely identified as CVE-2026-22396. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/28/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-3856). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
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: Resource injectionCWE: CWE-99
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
01/15/2026 Advisory disclosed01/15/2026 VulDB entry created
01/28/2026 VulDB entry last update
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2026-22396 (🔒)
GCVE (CVE): GCVE-0-2026-22396
GCVE (VulDB): GCVE-100-341259
EUVD: 🔒
Entry
Created: 01/15/2026 10:04Updated: 01/28/2026 11:52
Changes: 01/15/2026 10:04 (49), 01/27/2026 18:56 (1), 01/28/2026 11:52 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.