Automattic WooCommerce Plugin up to 4.6.x on WordPress Order Status fetch_order_status order_id information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Automattic WooCommerce Plugin up to 4.6.x on WordPress. It has been classified as problematic. This impacts the function fetch_order_status of the component Order Status Handler. Performing a manipulation of the argument order_id results in information disclosure.
This vulnerability is reported as CVE-2020-29156. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Automattic WooCommerce Plugin up to 4.6.x on WordPress (E-Commerce Management Software). It has been classified as problematic. This affects the function fetch_order_status of the component Order Status Handler. The manipulation of the argument order_id with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.
The weakness was disclosed 12/28/2020. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-29156. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 4.7.0 eliminates this vulnerability. The upgrade is hosted for download at raw.githubusercontent.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WooCommerce Plugin 4.7.0
Timeline
12/28/2020 🔍12/28/2020 🔍
12/28/2020 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2020-29156 (🔍)
GCVE (CVE): GCVE-0-2020-29156
GCVE (VulDB): GCVE-100-166857
Entry
Created: 12/28/2020 09:56Changes: 12/28/2020 09:56 (43)
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.