This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Dsmall
dsmall v20180320 allows XSS via the pdr_sn parameter to public/index.php/home/predeposit/index.html. (2018-04-04, CVE-2018-9307)
dsmall v20180320 allows XSS via the main page search box at the public/index.php/home URI. (2018-03-25, CVE-2018-9016)
dsmall v20180320 allows XSS via the member search box at the public/index.php/home/membersnsfriend/findlist.html URI. (2018-03-25, CVE-2018-9017)
dsmall v20180320 allows XSS via the public/index.php/home/predeposit/index.html pdr_sn parameter (aka the CMS search box). (2018-03-25, CVE-2018-9015)
dsmall v20180320 has XSS via a crafted street address to public/index.php/home/memberaddress/index.html, which is mishandled at public/index.php/home/memberaddress/edit/address_id/2.html. (2018-03-22, CVE-2018-8906)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>