WooCommerce Instamojo Payment Gateway Plugin 1.0.7 on WordPress Purchase card/pay/.../amount sign Price input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WooCommerce Instamojo Payment Gateway Plugin 1.0.7 on WordPress. It has been rated as critical. Affected is an unknown function of the file card/pay/.../amount of the component Purchase Handler. This manipulation of the argument sign as part of Parameter causes input validation (Price). This vulnerability is registered as CVE-2019-14977. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical was found in WooCommerce Instamojo Payment Gateway Plugin 1.0.7 on WordPress (E-Commerce Management Software). Affected by this vulnerability is an unknown function of the file card/pay/.../amount of the component Purchase Handler. The manipulation of the argument sign as part of a Parameter leads to a input validation vulnerability (Price). The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
card/pay/.../amount in the WooCommerce Instamojo Payment Gateway plugin 1.0.7 for WordPress allows Parameter Tampering in the sign parameter, as demonstrated by purchasing an item for lower than the intended price.
The weakness was published 08/29/2019. This vulnerability is known as CVE-2019-14977 since 08/12/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: PriceClass: Input validation / Price
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
08/12/2019 🔍08/29/2019 🔍
08/30/2019 🔍
12/11/2023 🔍
Sources
Status: Not definedCVE: CVE-2019-14977 (🔍)
GCVE (CVE): GCVE-0-2019-14977
GCVE (VulDB): GCVE-100-141085
Entry
Created: 08/30/2019 07:10Updated: 12/11/2023 07:20
Changes: 08/30/2019 07:10 (38), 08/09/2020 18:25 (4), 12/11/2023 07:20 (8)
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.