| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ionize 1.0.8.1. Affected by this issue is some unknown functionality of the file application/config/config.php of the component String Handler. This manipulation causes an unknown weakness. This vulnerability is tracked as CVE-2022-26272. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in ionize 1.0.8.1. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the file application/config/config.php of the component String Handler. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 03/25/2022 as 403. The advisory is shared at github.com. This vulnerability is known as CVE-2022-26272 since 02/28/2022. Technical details are known, but no exploit is available.
By approaching the search of inurl:application/config/config.php it is possible to find vulnerable targets with Google Hacking.
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
Name
Version
Website
- Product: https://github.com/ionize/ionize/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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/28/2022 🔍03/25/2022 🔍
03/25/2022 🔍
03/27/2022 🔍
Sources
Product: github.comAdvisory: 403
Status: Confirmed
CVE: CVE-2022-26272 (🔍)
GCVE (CVE): GCVE-0-2022-26272
GCVE (VulDB): GCVE-100-195757
Entry
Created: 03/25/2022 07:02Updated: 03/27/2022 08:50
Changes: 03/25/2022 07:02 (36), 03/27/2022 08:50 (1)
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.