CuppaCMS 1.0 POST Request cuppa/api/index.php function privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in CuppaCMS 1.0. It has been declared as critical. The affected element is an unknown function of the file cuppa/api/index.php of the component POST Request Handler. Executing a manipulation of the argument function can lead to an unknown weakness. This vulnerability is tracked as CVE-2022-37191. No exploit exists.
Details
A vulnerability classified as critical was found in CuppaCMS 1.0. This vulnerability affects some unknown processing of the file cuppa/api/index.php of the component POST Request Handler. The manipulation of the argument function with an unknown input leads to a unknown weakness. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
The component "cuppa/api/index.php" of CuppaCMS v1.0 is Vulnerable to LFI. An authenticated user can read system files via crafted POST request using [function] parameter value as LFI payload.
The weakness was disclosed 09/14/2022 as 20. The advisory is available at github.com. This vulnerability was named CVE-2022-37191 since 08/01/2022. Technical details are known, but there is no available exploit.
By approaching the search of inurl:cuppa/api/index.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 best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
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: Partially
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
08/01/2022 🔍09/14/2022 🔍
09/14/2022 🔍
09/14/2022 🔍
Sources
Product: github.comAdvisory: 20
Status: Confirmed
CVE: CVE-2022-37191 (🔍)
GCVE (CVE): GCVE-0-2022-37191
GCVE (VulDB): GCVE-100-208522
Entry
Created: 09/14/2022 10:29Changes: 09/14/2022 10:29 (38)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.