Jupiter Theme 6.10.1 on WordPress AJAX Action plugin-management.php abb_remove_plugin access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Jupiter Theme 6.10.1 on WordPress. It has been rated as critical. This vulnerability affects the function abb_remove_plugin of the file framework/admin/control-panel/logic/plugin-management.php of the component AJAX Action Handler. The manipulation leads to access control.
This vulnerability is uniquely identified as CVE-2022-1658. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Jupiter Theme 6.10.1 on WordPress (WordPress Plugin) and classified as critical. This issue affects the function abb_remove_plugin of the file framework/admin/control-panel/logic/plugin-management.php of the component AJAX Action Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is integrity, and availability. The summary by CVE is:
Vulnerable versions of the Jupiter Theme (<= 6.10.1) allow arbitrary plugin deletion by any authenticated user, including users with the subscriber role, via the abb_remove_plugin AJAX action registered in the framework/admin/control-panel/logic/plugin-management.php file. Using this functionality, any logged-in user can delete any installed plugin on the site.
The weakness was disclosed 06/13/2022. The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2022-1658 since 05/10/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
By approaching the search of inurl:framework/admin/control-panel/logic/plugin-management.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
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (Wordfence): 🔍
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: Access controlCWE: CWE-284 / CWE-266
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
05/10/2022 🔍06/13/2022 🔍
06/13/2022 🔍
06/13/2022 🔍
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2022-1658 (🔍)
GCVE (CVE): GCVE-0-2022-1658
GCVE (VulDB): GCVE-100-201677
Entry
Created: 06/13/2022 20:13Changes: 06/13/2022 20:13 (49), 06/13/2022 20:15 (2)
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.