Magento up to 2.2.9/2.3.2 Product Stored cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Magento up to 2.2.9/2.3.2. It has been classified as problematic. Impacted is an unknown function of the component Product Handler. The manipulation leads to cross site scripting (Stored). This vulnerability is listed as CVE-2019-8145. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as problematic, has been found in Magento up to 2.2.9/2.3.2. This issue affects an unknown code block of the component Product Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability (Stored). Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
A stored cross-site scripting (XSS) vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user can inject arbitrary JavaScript code into the attribute set name when listing the products.
The weakness was presented 11/06/2019. The identification of this vulnerability is CVE-2019-8145 since 02/12/2019. The attack may be initiated remotely. The requirement for exploitation is a simple authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 2.2.10, 2.3.2-p1 or 2.3.3 eliminates this vulnerability.
See VDB-145076, VDB-145075, VDB-145074 and VDB-145072 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: StoredClass: Cross site scripting / Stored
CWE: CWE-79 / CWE-94 / CWE-74
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: Magento 2.2.10/2.3.2-p1/2.3.3
Timeline
02/12/2019 🔍11/06/2019 🔍
11/06/2019 🔍
02/05/2024 🔍
Sources
Advisory: magento.comStatus: Not defined
CVE: CVE-2019-8145 (🔍)
GCVE (CVE): GCVE-0-2019-8145
GCVE (VulDB): GCVE-100-145073
See also: 🔍
Entry
Created: 11/06/2019 11:33 AMUpdated: 02/05/2024 08:13 AM
Changes: 11/06/2019 11:33 AM (38), 11/06/2019 11:38 AM (17), 02/05/2024 08:13 AM (4)
Complete: 🔍
Cache ID: 244:210:40
No comments yet. Languages: en.
Please log in to comment.