techjewel FluentSMTP Plugin up to 2.2.82 on WordPress deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in techjewel FluentSMTP Plugin up to 2.2.82 on WordPress. It has been classified as critical. Affected is an unknown function. This manipulation causes deserialization. This vulnerability is registered as CVE-2024-9511. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in techjewel FluentSMTP Plugin up to 2.2.82 on WordPress. It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The FluentSMTP – WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.2.82 via deserialization of untrusted input in the 'formatResult' function. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. The vulnerability was partially patched in version 2.2.82.
The weakness was published by Leo Trinh as 3194359. It is possible to read the advisory at wordfence.com. This vulnerability is known as CVE-2024-9511 since 10/04/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.
Upgrading eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 2.2.0
- 2.2.1
- 2.2.2
- 2.2.3
- 2.2.4
- 2.2.5
- 2.2.6
- 2.2.7
- 2.2.8
- 2.2.9
- 2.2.10
- 2.2.11
- 2.2.12
- 2.2.13
- 2.2.14
- 2.2.15
- 2.2.16
- 2.2.17
- 2.2.18
- 2.2.19
- 2.2.20
- 2.2.21
- 2.2.22
- 2.2.23
- 2.2.24
- 2.2.25
- 2.2.26
- 2.2.27
- 2.2.28
- 2.2.29
- 2.2.30
- 2.2.31
- 2.2.32
- 2.2.33
- 2.2.34
- 2.2.35
- 2.2.36
- 2.2.37
- 2.2.38
- 2.2.39
- 2.2.40
- 2.2.41
- 2.2.42
- 2.2.43
- 2.2.44
- 2.2.45
- 2.2.46
- 2.2.47
- 2.2.48
- 2.2.49
- 2.2.50
- 2.2.51
- 2.2.52
- 2.2.53
- 2.2.54
- 2.2.55
- 2.2.56
- 2.2.57
- 2.2.58
- 2.2.59
- 2.2.60
- 2.2.61
- 2.2.62
- 2.2.63
- 2.2.64
- 2.2.65
- 2.2.66
- 2.2.67
- 2.2.68
- 2.2.69
- 2.2.70
- 2.2.71
- 2.2.72
- 2.2.73
- 2.2.74
- 2.2.75
- 2.2.76
- 2.2.77
- 2.2.78
- 2.2.79
- 2.2.80
- 2.2.81
- 2.2.82
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
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: DeserializationCWE: CWE-502 / CWE-20
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
10/04/2024 🔍11/23/2024 🔍
11/23/2024 🔍
11/23/2024 🔍
Sources
Advisory: 3194359Researcher: Leo Trinh
Status: Confirmed
CVE: CVE-2024-9511 (🔍)
GCVE (CVE): GCVE-0-2024-9511
GCVE (VulDB): GCVE-100-285955
Entry
Created: 11/23/2024 11:26Changes: 11/23/2024 11:26 (65)
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.