PrestaShop up to 1.7.6.4 back Reflected cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in PrestaShop 1.7.6.0/1.7.6.1/1.7.6.2/1.7.6.3/1.7.6.4. This issue affects some unknown processing. Performing a manipulation of the argument back as part of Parameter results in cross site scripting (Reflected). This vulnerability is known as CVE-2020-5285. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in PrestaShop 1.7.6.0/1.7.6.1/1.7.6.2/1.7.6.3/1.7.6.4 (E-Commerce Management Software). This affects some unknown processing. The manipulation of the argument back as part of a Parameter leads to a cross site scripting vulnerability (Reflected). CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:
In PrestaShop between versions 1.7.6.0 and 1.7.6.5, there is a reflected XSS with `back` parameter. The problem is fixed in 1.7.6.5
The weakness was published 04/20/2020 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-5285 since 01/02/2020. It is possible to initiate the attack remotely. Required for exploitation is a authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 1.7.6.5 eliminates this vulnerability.
Similar entries are available at VDB-154129, VDB-154128, VDB-154127 and VDB-154126. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.1
NVD Vector: 🔍
CNA Base Score: 4.1
CNA Vector (GitHub, Inc.): 🔍
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: ReflectedClass: Cross site scripting / Reflected
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: PrestaShop 1.7.6.5
Patch: github.com
Timeline
01/02/2020 🔍04/20/2020 🔍
04/21/2020 🔍
05/06/2025 🔍
Sources
Product: github.comAdvisory: b6aea152988d81e1586f1c03f2e72c9ef2fe7df7
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-5285 (🔍)
GCVE (CVE): GCVE-0-2020-5285
GCVE (VulDB): GCVE-100-154125
See also: 🔍
Entry
Created: 04/21/2020 08:12Updated: 05/06/2025 16:02
Changes: 04/21/2020 08:12 (41), 04/21/2020 08:17 (12), 10/10/2020 16:14 (1), 10/10/2020 16:22 (1), 06/01/2024 09:05 (18), 06/01/2024 09:08 (17), 05/06/2025 16:02 (7)
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.