CVE-2020-15178 json
Potential XSS in PrestaShop contactform
published 2020-09-15 6 y ago modified 2026-09-10 1 mo ago also GHSA-95hx-62rh-gg96 , EUVD-2020-0925
- cvss
- 8.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist prestashop/contactform 4.3.0
- prestashop contactform 4.3.0
Exploit prediction
1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 9.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | prestashop/contactform | >=1.0.1, <4.3.0 |
4.3.0 |
Affected products
- PrestaShop contactform
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/PrestaShop/contactform/commit/ecd9f5d14920ec00885766a7cb41bcc5ed8bfa09
web, patch, third-party-advisory
-
github.com
/PrestaShop/contactform/commit/a1da814bea7e5750b858a2dbbc58ace80379f42f
web
-
packagist.org
/packages/prestashop/contactform
web, vendor-advisory
-
github.com
/PrestaShop/contactform/security/advisories/GHSA-95hx-62rh-gg96
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15178
advisory
-
github.com
/PrestaShop/contactform
package
Sources
- CVE List CVE-2020-15178
- GitHub Advisory GHSA-95hx-62rh-gg96
- NVD CVE-2020-15178
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.