YaySMTP Plugin up to 2.2.0 on WordPress Log authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in YaySMTP Plugin up to 2.2.0 on WordPress. The impacted element is an unknown function of the component Log Handler. Performing a manipulation results in authorization. This vulnerability is reported as CVE-2022-2369. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in YaySMTP Plugin up to 2.2.0 on WordPress (WordPress Plugin). It has been classified as problematic. This affects an unknown code of the component Log Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:
The YaySMTP WordPress plugin before 2.2.1 does not have capability check in an AJAX action, allowing any logged in users, such as subscriber to view the Logs of the plugin
The weakness was disclosed 08/01/2022. The advisory is shared at wpscan.com. This vulnerability is uniquely identified as CVE-2022-2369 since 07/11/2022. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.2.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.9VulDB Meta Temp Score: 3.8
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD 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: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
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: 🔍
Upgrade: YaySMTP Plugin 2.2.1
Timeline
07/11/2022 🔍08/01/2022 🔍
08/01/2022 🔍
08/29/2022 🔍
Sources
Advisory: wpscan.comStatus: Confirmed
CVE: CVE-2022-2369 (🔍)
GCVE (CVE): GCVE-0-2022-2369
GCVE (VulDB): GCVE-100-205377
Entry
Created: 08/01/2022 17:20Updated: 08/29/2022 09:36
Changes: 08/01/2022 17:20 (40), 08/29/2022 09:36 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.