Reporter David Sopas
`PrestaShop <= 1.5.1 Persistent XSS
Tested under: Firefox, Chrome and Safari latest versions
Discover Credits: David Sopas - firstname.lastname@example.org | @dsopas |
Original link: http://davidsopas.com/labs/prestashop_xss.txt
PrestaShop is the most reliable and flexible Open-source e-commerce
software. Since 2007,
PrestaShop has revolutionized the industry by providing features that
engage shoppers and
increase online sales. The Prestateam consists of over 100 passionate
individuals and more
than 350,000 community members dedicated to innovated technology.
It has more than 2.000.000 downloads and won the best open-source
e-commerce software in
the last few years.
When installing and analyzing PrestaShop on a secure environment I
discovered that it's
possible to bypass isCleanHtml() function, used in many places, in
this case in particular
the Contact Form.
A user could use this vulnerability, a Persistent Cross-site
Scripting, to execute malicious
payloads on admins message box.
Proof of concept:
In the message field a user could write:
JpcHQ+PC9zdmc+' type='image/svg+xml' AllowScriptAccess='always'></embed>
Both Base64 strings are mainly <script>alert()</script> encoded.
Those XSS vectors bypass the filter on isCleanHtml() and execute
automatically when the admin
check the messages on the admin area. This is critical and could be
used to implement very
Keep in mind that on some webmail variations, the code is also
executed. A user can even play
with heading <h1> and other HTML on message box.
<a href="#" target="_blank"><img
height="600px" border="0" /></a>
<a href="#" target="_blank" style="font-size: 30px">Click here</a>
Again, encoding with Base64 could also obfuscate a little bit.
I think that in this case in particular, HTML should be stripped out
because it has no meaning
in my opinion on the contact form.
Solution: Vendor reported that upgrading PrestaShop to version 1.5.2
will fix admins message
HTML on email accounts still a possibility in the latest version.
According to the vendor,
it will be fixed on the next version.
email@example.com # @dsopas