Automattic WooPayments Plugin up to 6.9.2 on WordPress authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Automattic WooPayments Plugin up to 6.9.2 on WordPress. It has been rated as problematic. The affected element is an unknown function. The manipulation leads to authorization. This vulnerability is documented as CVE-2023-51503. The attack can be initiated remotely. There is not any exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Automattic WooPayments Plugin up to 6.9.2 on WordPress (WordPress Plugin) and classified as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality. The summary by CVE is:
Authorization Bypass Through User-Controlled Key vulnerability in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo.This issue affects WooPayments – Fully Integrated Solution Built and Supported by Woo: from n/a through 6.9.2.
The weakness was released 01/01/2024 by Rafie Muhammad. It is possible to read the advisory at patchstack.com. The identification of this vulnerability is CVE-2023-51503 since 12/20/2023. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/22/2024).
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
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.9
CNA Vector (Patchstack): 🔍
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-639 / CWE-285 / CWE-266
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
12/20/2023 🔍12/31/2023 🔍
01/01/2024 🔍
01/22/2024 🔍
Sources
Advisory: patchstack.comResearcher: Rafie Muhammad
Status: Not defined
CVE: CVE-2023-51503 (🔍)
GCVE (CVE): GCVE-0-2023-51503
GCVE (VulDB): GCVE-100-249431
Entry
Created: 01/01/2024 12:25 AMUpdated: 01/22/2024 11:38 AM
Changes: 01/01/2024 12:25 AM (50), 01/22/2024 11:38 AM (11)
Complete: 🔍
Cache ID: 244:881:40
No comments yet. Languages: en.
Please log in to comment.