Filtered by vendor Prestashop
Subscribe
Total
116 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2020-5270 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 5.8 MEDIUM | 4.1 MEDIUM |
In PrestaShop between versions 1.7.6.0 and 1.7.6.5, there is an open redirection when using back parameter. The impacts can be many, and vary from the theft of information and credentials to the redirection to malicious websites containing attacker-controlled content, which in some cases even cause XSS attacks. So even though an open redirection might sound harmless at first, the impacts of it can be severe should it be exploitable. The problem is fixed in 1.7.6.5 | |||||
CVE-2020-5269 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 4.3 MEDIUM | 4.1 MEDIUM |
In PrestaShop between versions 1.7.6.1 and 1.7.6.5, there is a reflected XSS on AdminFeatures page by using the `id_feature` parameter. The problem is fixed in 1.7.6.5 | |||||
CVE-2020-5266 | 1 Prestashop | 1 Prestashop Link | 2024-11-21 | 3.5 LOW | 4.4 MEDIUM |
In the ps_link module for PrestaShop before version 3.1.0, there is a stored XSS when you create or edit a link list block with the title field. The problem is fixed in 3.1.0 | |||||
CVE-2020-5265 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 4.3 MEDIUM | 4.4 MEDIUM |
In PrestaShop between versions 1.7.6.1 and 1.7.6.5, there is a reflected XSS on AdminAttributesGroups page. The problem is patched in 1.7.6.5. | |||||
CVE-2020-5264 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 4.3 MEDIUM | 4.4 MEDIUM |
In PrestaShop before version 1.7.6.5, there is a reflected XSS while running the security compromised page. It allows anyone to execute arbitrary action. The problem is patched in the 1.7.6.5. | |||||
CVE-2020-5250 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 4.9 MEDIUM | 7.6 HIGH |
In PrestaShop before version 1.7.6.4, when a customer edits their address, they can freely change the id_address in the form, and thus steal someone else's address. It is the same with CustomerForm, you are able to change the id_customer and change all information of all accounts. The problem is patched in version 1.7.6.4. | |||||
CVE-2020-4074 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 10.0 HIGH | 8.9 HIGH |
In PrestaShop from version 1.5.0.0 and before version 1.7.6.6, the authentication system is malformed and an attacker is able to forge requests and execute admin commands. The problem is fixed in 1.7.6.6. | |||||
CVE-2020-26248 | 1 Prestashop | 1 Productcomments | 2024-11-21 | 6.4 MEDIUM | 6.8 MEDIUM |
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module. | |||||
CVE-2020-26225 | 1 Prestashop | 1 Product Comments | 2024-11-21 | 4.3 MEDIUM | 8.7 HIGH |
In PrestaShop Product Comments before version 4.2.0, an attacker could inject malicious web code into the users' web browsers by creating a malicious link. The problem was introduced in version 4.0.0 and is fixed in 4.2.0 | |||||
CVE-2020-26224 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
In PrestaShop before version 1.7.6.9 an attacker is able to list all the orders placed on the website without being logged by abusing the function that allows a shopping cart to be recreated from an order already placed. The problem is fixed in 1.7.6.9. | |||||
CVE-2020-21967 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 3.5 LOW | 4.8 MEDIUM |
File upload vulnerability in the Catalog feature in Prestashop 1.7.6.7 allows remote attackers to run arbitrary code via the add new file page. | |||||
CVE-2020-15178 | 1 Prestashop | 1 Contactform | 2024-11-21 | 4.3 MEDIUM | 8.0 HIGH |
In PrestaShop contactform module (prestashop/contactform) before version 4.3.0, an attacker is able to inject JavaScript while using the contact form. The `message` field was incorrectly unescaped, possibly allowing attackers to execute arbitrary JavaScript in a victim's browser. | |||||
CVE-2020-15162 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 3.5 LOW | 5.4 MEDIUM |
In PrestaShop from version 1.5.0.0 and before version 1.7.6.8, users are allowed to send compromised files. These attachments allowed people to input malicious JavaScript which triggered an XSS payload. The problem is fixed in version 1.7.6.8. | |||||
CVE-2020-15161 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 4.3 MEDIUM | 5.4 MEDIUM |
In PrestaShop from version 1.6.0.4 and before version 1.7.6.8 an attacker is able to inject javascript while using the contact form. The problem is fixed in 1.7.6.8 | |||||
CVE-2020-15160 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
PrestaShop from version 1.7.5.0 and before version 1.7.6.8 is vulnerable to a blind SQL Injection attack in the Catalog Product edition page with location parameter. The problem is fixed in 1.7.6.8 | |||||
CVE-2020-15102 | 1 Prestashop | 1 Dashboard Products | 2024-11-21 | 4.0 MEDIUM | 6.5 MEDIUM |
In PrestaShop Dashboard Productions before version 2.1.0, there is improper authorization which enables an attacker to change the configuration. The problem is fixed in 2.1.0. | |||||
CVE-2020-15083 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 4.3 MEDIUM | 4.7 MEDIUM |
In PrestaShop from version 1.7.0.0 and before version 1.7.6.6, if a target sends a corrupted file, it leads to a reflected XSS. The problem is fixed in 1.7.6.6 | |||||
CVE-2020-15082 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 7.5 HIGH | 7.1 HIGH |
In PrestaShop from version 1.6.0.1 and before version 1.7.6.6, the dashboard allows rewriting all configuration variables. The problem is fixed in 1.7.6.6 | |||||
CVE-2020-15081 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 5.0 MEDIUM | 5.3 MEDIUM |
In PrestaShop from version 1.5.0.0 and before 1.7.6.6, there is information exposure in the upload directory. The problem is fixed in version 1.7.6.6. A possible workaround is to add an empty index.php file in the upload directory. | |||||
CVE-2020-15080 | 1 Prestashop | 1 Prestashop | 2024-11-21 | 5.0 MEDIUM | 5.3 MEDIUM |
In PrestaShop from version 1.7.4.0 and before version 1.7.6.6, some files should not be in the release archive, and others should not be accessible. The problem is fixed in version 1.7.6.6 A possible workaround is to make sure `composer.json` and `docker-compose.yml` are not accessible on your server. |