AI Power Plugin up to 1.8.96 on WordPress server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in AI Power Plugin up to 1.8.96 on WordPress. This affects an unknown part. The manipulation leads to server-side request forgery. This vulnerability is uniquely identified as CVE-2024-13360. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in AI Power Plugin up to 1.8.96 on WordPress. It has been rated as critical. This issue affects an unknown code. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The AI Power: Complete AI Pack plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.8.96 via the wpaicg_troubleshoot_add_vector(). This makes it possible for authenticated attackers, with subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2024-13360 since 01/13/2025. The exploitation is known to be easy. The attack may be initiated remotely. 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 01/22/2025).
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
- 1.8.0
- 1.8.1
- 1.8.2
- 1.8.3
- 1.8.4
- 1.8.5
- 1.8.6
- 1.8.7
- 1.8.8
- 1.8.9
- 1.8.10
- 1.8.11
- 1.8.12
- 1.8.13
- 1.8.14
- 1.8.15
- 1.8.16
- 1.8.17
- 1.8.18
- 1.8.19
- 1.8.20
- 1.8.21
- 1.8.22
- 1.8.23
- 1.8.24
- 1.8.25
- 1.8.26
- 1.8.27
- 1.8.28
- 1.8.29
- 1.8.30
- 1.8.31
- 1.8.32
- 1.8.33
- 1.8.34
- 1.8.35
- 1.8.36
- 1.8.37
- 1.8.38
- 1.8.39
- 1.8.40
- 1.8.41
- 1.8.42
- 1.8.43
- 1.8.44
- 1.8.45
- 1.8.46
- 1.8.47
- 1.8.48
- 1.8.49
- 1.8.50
- 1.8.51
- 1.8.52
- 1.8.53
- 1.8.54
- 1.8.55
- 1.8.56
- 1.8.57
- 1.8.58
- 1.8.59
- 1.8.60
- 1.8.61
- 1.8.62
- 1.8.63
- 1.8.64
- 1.8.65
- 1.8.66
- 1.8.67
- 1.8.68
- 1.8.69
- 1.8.70
- 1.8.71
- 1.8.72
- 1.8.73
- 1.8.74
- 1.8.75
- 1.8.76
- 1.8.77
- 1.8.78
- 1.8.79
- 1.8.80
- 1.8.81
- 1.8.82
- 1.8.83
- 1.8.84
- 1.8.85
- 1.8.86
- 1.8.87
- 1.8.88
- 1.8.89
- 1.8.90
- 1.8.91
- 1.8.92
- 1.8.93
- 1.8.94
- 1.8.95
- 1.8.96
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector: 🔍
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: Server-side request forgeryCWE: CWE-918
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/13/2025 🔍01/21/2025 🔍
01/21/2025 🔍
01/22/2025 🔍
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2024-13360 (🔍)
GCVE (CVE): GCVE-0-2024-13360
GCVE (VulDB): GCVE-100-292877
Entry
Created: 01/21/2025 23:01Updated: 01/22/2025 09:45
Changes: 01/21/2025 23:01 (51), 01/22/2025 09:45 (12)
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.